[WG: I18N & L10N] My plan for smoothly including Pearsons' translations

Shoji Kajita kajita.shoji.5z at kyoto-u.ac.jp
Fri Jul 12 07:21:12 PDT 2013


Hi Jean-Francois,

I have understood your situation. It is quite reasonable.

As for ja_JP_Pearsons, I hope Yuji, the chair of Ja Sakai, can answer.

Best regards,
Shoji

At Fri, 12 Jul 2013 10:43:24 +0200,
Jean-Francois Leveque wrote:
> 
> Hi Shoji,
> 
> I've been told the French translation was incomplete and this was 
> annoying users who rely on it outside of France.
> 
> I'm trying to lower the barrier for those who would like to benefit from 
> Pearson's translation. It seem to me that putting it into contrib or 
> msub won't lower the barrier.
> 
> Gao Jun asked me not to do this for the zh_CN translation because he 
> will provide a better one soon. Because I haven't heard about requests 
> for using Pearson's zh_CN translation, I think I can wait for his update.
> 
> I haven't heard heard about requests for using Pearson's ja_JP 
> translation, I can also not create a ja_JP_Pearson locale variant and 
> wait for an update if the Japanese community asks.
> 
> To manage the variants that do not increase the translation coverage, I 
> would ask the institutions that need those to do the updates in 
> subversion themselves. Training and help could be provided by volunteers 
> who already know how to do this. Do you have another idea in mind?
> 
> J-F
> 
> On 11/07/2013 16:34, Shoji Kajita wrote:
> > Hi Jean-Francois,
> >
> > I think Pearsons' translations should be in contrib or msub at first,
> > as in the case of 'code'.
> >
> > In Japan, ja_JP (or ja) is now under the control of Ja Sakai
> > Community. But we, Kyoto University, need to revise several words and
> > phrases due to Kyoto University's local culture. I think the best way
> > to manage such localized bundles is using a variant of locale like
> > ja_JP_Kyoto as you suggested
> >
> > In this sense, I think there will be a lot of variants of locale in
> > the future something like:
> >
> >    en_US_umich, en_GB_hull, ja_JP_K12, ...
> >
> > I think we need to find a way to manage these locale with variant.
> >
> > Shoji
> >
> > At Wed, 10 Jul 2013 12:21:21 +0200,
> > Jean-Francois Leveque wrote:
> >>
> >> Hi,
> >>
> >> As written under 'Managing translation updates' two months ago, I was
> >> wondering how to benefit from Pearsons' translations without disturbing
> >> the maintained translations.
> >>
> >> For the languages that are maintained and whose maintainers want to
> >> review the contributed translations, I plan to add the translations to a
> >> variant of the locale<language>_<country>_Pearson.
> >>
> >> For the languages that are not maintained or whose maintainers do not
> >> mind getting the contributed translations as is, I plan to replace the
> >> current translations with the contributed ones.
> >>
> >> Here is a list of the new variant locales with Pearson's translations:
> >> es_ES_Pearson
> >> fr_CA_Pearson
> >> fr_FR_Pearson
> >> ja_JP_Pearson
> >> nl_NL_Pearson
> >> zh_CN_Pearson
> >>
> >> Here is a list of the locales that will have their translations, when
> >> available, replaced by Pearson's:
> >> de
> >> en_GB
> >> it
> >> ko
> >> pt_BR
> >> pt_PT
> >> zh_TW
> >>
> >> Please correct me if I misunderstood the information I got about the
> >> locale you're maintaining.
> >>
> >> Please feel free to ask questions too.
> >>
> >> If all is fine, I plan to revert the translation inclusions that were
> >> done before and add them again as planned above unless I see approval
> >> comments by locale maintainer in the corresponding JIRA issue.
> >>
> >> Cheers,
> >> --
> >> Jean-François


More information about the i18n mailing list