[WG: I18N & L10N] On the integration of translations
jean-francois.leveque at upmc.fr
Tue Mar 19 02:47:55 PDT 2013
Your suggestion is welcome, Sam. I think I can't use it as is.
I'm afraid we're currently short on resources, even for the role I have. :(
This WG works both on i18n an L10n. Translations are only in the L10n part.
Most of the time, translation contributions have no issues and most of
the issues found in the translations, AFAICT, are related to i18n issues.
I would like to be able to check updated translation files automagically
but I didn't have much time to think about how to do this.
As long as I don't have script/binary magic to do this, this can be time
So far, only the institutions using mostly the bugged locales are hurt,
this means the contributors of those translations and maybe other
institutions in the same country.
I'm afraid i18n issues, which I'm doing my best to distinguish from L10n
issues, hurt all the institutions that are not using CLE in English only
with the default translation.
That's why I think I should do my best to spend more time on i18n than I
spend on L10n.
When L10n issues are found, I will nevertheless help the best I can.
I welcome both support and contradiction and I'll be glad to get help.
I thank Beth for her help in this transition time.
On 18/03/2013 17:56, Sam Ottenhoff wrote:
> If you know none, I suggest you do the testing and set the issues as
> Verified if tests pass.
> Or I would suggest the i18n coordinator review the patch or commit and
> confirm everything was done correctly. There have been several cases of
> incorrect internationalization patches applied to trunk over the past
> several months. Polish and Swedish recent translations contained bad
More information about the i18n