I just had a look at StructureStrings.properties and it appears that
there is no translation whatsoever. The question is, should we really
start to translate framework messages, i.e. messages that aren't
presented to the user, into other languages? One could argue that a
programmer should have enough english language skills to understand those...
Uli
Howard Lewis Ship schrieb:
I think add it, and add a new issue requesting translations. The new
issue can be broken into tasks per supported language. As it annoys
people, they'll provide translations :-)
On Sun, Feb 1, 2009 at 4:20 PM, Kevin Menard <[email protected]> wrote:
What's the general policy on adding i18n strings? E.g., I'd like to
add a new one for TAP5-151, but I'm only going to be able to provide
an English translation to start.
Should I keep the issue open until all translations are in? Should I
open a new issue requesting that string to be translated? Or is there
some other procedure to follow?
--
Thanks,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
