| Re: [babel-translators] CVS decorators |
Kit Lo schreef:
>
> 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".
Good to know, but then Iâd like another checkbox in the interface to
mark a string non-translatable system-wide. For example, all
âEclipse.orgâ strings should be never translated in any language. I
have been marking them, thinking this worked for everyone, but if it is
only for Dutch, that takes away much of my motivation.
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
Description: OpenPGP digital signature