Re: [babel-translators] CVS decorators

[Kit Lo <kitlo@xxxxxxxxxx>]

Denis was right along the line, but
his example may not be very good :-) I will try another example, but mine
may not be perfect either :-)

Let's say there is a string:
name={0} {1}
where {0} is the first name and {1}
is the last name

There is nothing to translate in this
string, and for most languages they should not have to doing anything.
But, for Asian languages, they may want to swap the first name and last
name to make it look like:
name={1} {0}

Therefore, "non-translatable"
is language dependent.

>Arens plugin developers supposed
to mark strings non-translatable?
There are 2 kinds of "non-translatable"
strings. There are some string that developers use for initialization,
constants, etc, that should never be touched, or else the program may not
work properly. Developers will mark these strings "non-translatable".
Technically, we should not even import these strings into the translation
server and present to the translators. Babel has an open bug for this but
we did not have that implemented yet. Patch contribution is welcomed :-)

The second kind of "non-translatable"
strings is determined by translators. If the translator for a language
thinks that the string should not be translated in their language, the
translator should mark it as "non-translatable".

Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead

Hendrik Maryns <hamaryns@xxxxxxxxxxxxxx>
Sent by: babel-translators-bounces@xxxxxxxxxxx

01/21/2009 12:14 PM

Please respond to
Mailing list for Babel translators <babel-translators@xxxxxxxxxxx>

To	Mailing list for Babel translators <babel-translators@xxxxxxxxxxx>
cc
Subject	Re: [babel-translators] CVS decorators

Denis Roy schreef:
> Hendrik Maryns wrote:
>> Paulo Moreira schreef:
>>   
>>> Hi Denis,
>>>
>>> What will hapen if i mark the Non-Translatable box ? (at the
left-down
>>> corner).
>>>     
>>
>> Yes, why not simply mark it non-translatable?
>>
>> H.
>>   
> If that is appropriate for your locale, then go ahead and mark it
> non-translatable.  However, if you're in a RTL locale, perhaps
> 
> {outgoing_change_flag}{name} {revision} {tag}
> 
> could be
> {tag} {revision} {name}{outgoing_change_flag}
> 
> 
> Perhaps this is a bad example, but I asked Kit a long time ago why
some
> file names (such as image names) were externalized (image1.jpg, for
> instance) and he explained that externalizing some seemingly
> non-translateable elements allows for different elements in various
> locales (image_fr.jpg, for instance).
> 
> 
> Again, if non-translatable is appropriate for your locale, go ahead.

This is interesting.  I thought non-translatable was system-wide,
not
language-dependent.  Is it?  Aren’s plugin developers supposed
to mark
strings non-translatable?

H.
-- 
Hendrik Maryns
Herrenberger Straße 40
D-72070 Tübingen
+49707143783
http://tcl.sfs.uni-tuebingen.de/~hendrik/
=================
www.lieverleven.be     Hier kan iedereen wat van leren.


[attachment "signature.asc" deleted by Kit Lo/Raleigh/IBM] _______________________________________________
babel-translators mailing list
babel-translators@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-translators