[ omegat-Bugs-1604169 ] file name fields in file filters should be localizable

[SourceForge.net <no...@so...>]

Bugs item #1604169, was opened at 2006-11-28 02:04
Message generated for change (Comment added) made by henry_pijffers
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520347&aid=1604169&group_id=68187

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: localization
Group: 1.6
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
Summary: file name fields in file filters should be localizable

Initial Comment:
the contents of:
${nameOnly}
${targetLanguage}
${extension}

namely the part btween ${ and } should be localizable.

----------------------------------------------------------------------

>Comment By: Henry Pijffers (henry_pijffers)
Date: 2006-11-30 10:10

Message:
Logged In: YES 
user_id=545103
Originator: NO

GUI strings are different. They're just strings displayed on the screen,
whereas parameter strings are entered by the user, and parsed by the
program code. If the user enteres something unexpected, the program will
malfunction, whereas if a GUI string is in a different, but intelligible
language, the program will still function properly.

If I, as a French user, start OmegaT and my (French) GUI says "Cherchez
exactement" (pardon my French), while my (English) manual says "Exact
search", it's obvious to me what was intended, and I will have no problem
using the program.

However, if my (English) manual says I must insert "${nameOnly}" in a
certain editable field, then I do that. And then I, as a "French" user,
will either get nothing or a whole bunch of errors, because the program
was expecting "${seulementNom}". There was no indication whatsoever that I
should've entered something French. And even if I realised that I should
enter something French, then I couldn't know what to enter exactly, I
could only make guesses (or, if I were smart, open up Bundle_fr.properties
and look there). I would be unable to use that aspect of the program.

Think of what would happen if people would localise any programming
language. Microsoft has some experience with that. They localised VB, and
look what it brought them... Dozens (or should I say thousands?) of
incompatible macros, only because they used different languages. So they
went back to English only.

Or think of what would happen if people would localise the tags in XML
files. I envision numerous browser horror stories popping up all over the
Internet.

----------------------------------------------------------------------

Comment By: Jean-Christophe Helary (brandelune)
Date: 2006-11-30 09:29

Message:
Logged In: YES 
user_id=915082
Originator: YES

well, but that is the case for any GUI string in OmegaT. If the string is
translated but not the reference to the string in the manual then problems
occur. But those are localization bugs, not application bugs and should be
taken care of by localizers.


----------------------------------------------------------------------

Comment By: Henry Pijffers (henry_pijffers)
Date: 2006-11-30 09:22

Message:
Logged In: YES 
user_id=545103
Originator: NO

I understand your desire to use parameters in one's own language. However,
making these localisable, could introduce unexpected errors. 

Suppose a Frenchman creates a minimal localisation, including ${nameOnly}
to ${seulementNom}, but doesn't translate the manual. Then the French user
is stuck with an English manual, telling him to insert ${nameOnly}, whereas
the program is expecting ${seulementNom}.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520347&aid=1604169&group_id=68187