Re: [Sugar-devel] [SLOBS] [Localization] Translations
For javascript L10n, start with these links: http://www.localeplanet.com/ https://blog.mozilla.org/webdev/2011/10/06/i18njs-internationalize-your-javascript-with-a-little-help-from-json-and-the-server/ cjl On Sat, Feb 20, 2016 at 7:14 PM, Walter Bender wrote: > Another hole in the i18n infrastructure is with our Javascript activities. > Maybe worth a GSOC project to shore it up. > > On Feb 20, 2016 3:58 PM, "Chris Leonard" wrote: >> >> Comments included in-line below >> >> On Sat, Feb 20, 2016 at 3:35 AM, Tony Anderson >> wrote: >> > As I understand the issue: SugarLabs has some funds available to support >> > translation of Sugar. At the SLOBs meeting, it was proposed that >> > SugarLabs recruit a 'translation manager', a possibly paid position. One >> > question is the job description for this role. >> >> For quite some time (starting in 2008, as I recall) under the "title" >> of Translation Team Coordinator I worked in that role (unpaid) and I >> can certainly help in fleshing out details. From 2008 - 2013 I was >> able to dedicate adequate time to both technical aspects of i18n >> (Pootle infrastructure and i18n advocacy/assistance to developers) as >> well as L10n (localization mailing list, maintain L10n wiki pages, >> support to new language communities, recruiting new localizers, etc.). >> The good news (for me) is that in 2013 an extended period of >> unemployment ended, the bad news is that I found myself unable to >> continue to provide sufficient support to the community for several >> reasons (technical issues with Pootle version migration as well as >> development migration to github beyond my scope to manage alone) and a >> slump in L10n activity by the community (perhaps in part because of >> insufficient efforts to organize and rally the troops). >> >> My employment situation has stabilized somewhat and I would like to >> continue to contribute to the i18n/L10n effort, but as many have >> experienced throughout the financial crisis, my new employment >> circumstances are only providing a fraction of the income I had made >> in the past, so my "free time" is subject to the demands of pursuing >> supplemental income. I have done some work in support of Sugar Labs >> since (e.g. Awajún glibc locale drafting), for which I might be >> compensated for my time and effort from the TripAdvisor grant based on >> a template agreement worked out with the SFC and the prior approval of >> the Sugar Labs Oversight Board. That is essentially piece-work, a >> pre-agreed amount for a pre-agreed deliverable (a committed glibc >> locale), I have not yet actually drawn any TripAdvsor funds for this >> purpose, but I may make such requests in future (assuming necessary >> pre-approvals are granted). >> >> >> > I would like to review the translation process: >> > >> > Translation has two separate parts: internationalization(I18n) and >> > localization (L10n). >> > >> > The Sugar-Devel team is responsible for I18n (preparing the framework to >> > support localization) and the community is responsible for L10n - >> > providing >> > translations (by default, from English) to other languages. >> >> Note: English is the original language of many activities, but there >> are also many written first in Spanish, working with developers to >> make Spanish-originating activities capable of being translated to >> other languages (via an English bridge) is an issue requiring >> attention. >> >> L10n leadership tasks: >> >> Monitoring new activity development and advocating for i18n of code >> (gettext formatting). >> >> Setting up new languages for availability in Pootle. >> >> Reaching upstream to create glibc locales for new languages. >> Necessary for them to be selectable languages in Linux-based systems. >> >> Requesting github permissions for the pootle git-hub user (to enable >> pull of new templates, push of completed translations). >> >> Monitoring Pootle for currency of templates, update of templates on >> existing languages, commit of new translations. Tasks technically the >> responsibility of individual language team leaders, but in practice >> needing an overseer on behalf of all languages. >> >> > The immediate focus is on using Pootle as the I18n framework with >> > translators providing the localization. >> > >> > Let's divide the languages into three groups: >> > >> > - English (the base language) >> > >> > - Mediums of instruction (languages used at deployments as a common >> > language where more than one language is spoken) >> > >> > - Local language (languages used by students at home) >> >> English is not always the base language of our South Amreican activity >> developers, as mentioned, this requires some careful thought and >> action to make these Spanish-originating activities more widely >> available in other languages. >> >> Fortunately, the Pootle system can take the ongoing Spanish >> translation of an English-originating activity and show it to >> indigenous language t
Re: [Sugar-devel] [SLOBS] [Localization] Translations
Another hole in the i18n infrastructure is with our Javascript activities. Maybe worth a GSOC project to shore it up. On Feb 20, 2016 3:58 PM, "Chris Leonard" wrote: > Comments included in-line below > > On Sat, Feb 20, 2016 at 3:35 AM, Tony Anderson > wrote: > > As I understand the issue: SugarLabs has some funds available to support > > translation of Sugar. At the SLOBs meeting, it was proposed that > > SugarLabs recruit a 'translation manager', a possibly paid position. One > > question is the job description for this role. > > For quite some time (starting in 2008, as I recall) under the "title" > of Translation Team Coordinator I worked in that role (unpaid) and I > can certainly help in fleshing out details. From 2008 - 2013 I was > able to dedicate adequate time to both technical aspects of i18n > (Pootle infrastructure and i18n advocacy/assistance to developers) as > well as L10n (localization mailing list, maintain L10n wiki pages, > support to new language communities, recruiting new localizers, etc.). > The good news (for me) is that in 2013 an extended period of > unemployment ended, the bad news is that I found myself unable to > continue to provide sufficient support to the community for several > reasons (technical issues with Pootle version migration as well as > development migration to github beyond my scope to manage alone) and a > slump in L10n activity by the community (perhaps in part because of > insufficient efforts to organize and rally the troops). > > My employment situation has stabilized somewhat and I would like to > continue to contribute to the i18n/L10n effort, but as many have > experienced throughout the financial crisis, my new employment > circumstances are only providing a fraction of the income I had made > in the past, so my "free time" is subject to the demands of pursuing > supplemental income. I have done some work in support of Sugar Labs > since (e.g. Awajún glibc locale drafting), for which I might be > compensated for my time and effort from the TripAdvisor grant based on > a template agreement worked out with the SFC and the prior approval of > the Sugar Labs Oversight Board. That is essentially piece-work, a > pre-agreed amount for a pre-agreed deliverable (a committed glibc > locale), I have not yet actually drawn any TripAdvsor funds for this > purpose, but I may make such requests in future (assuming necessary > pre-approvals are granted). > > > > I would like to review the translation process: > > > > Translation has two separate parts: internationalization(I18n) and > > localization (L10n). > > > > The Sugar-Devel team is responsible for I18n (preparing the framework to > > support localization) and the community is responsible for L10n - > providing > > translations (by default, from English) to other languages. > > Note: English is the original language of many activities, but there > are also many written first in Spanish, working with developers to > make Spanish-originating activities capable of being translated to > other languages (via an English bridge) is an issue requiring > attention. > > L10n leadership tasks: > > Monitoring new activity development and advocating for i18n of code > (gettext formatting). > > Setting up new languages for availability in Pootle. > > Reaching upstream to create glibc locales for new languages. > Necessary for them to be selectable languages in Linux-based systems. > > Requesting github permissions for the pootle git-hub user (to enable > pull of new templates, push of completed translations). > > Monitoring Pootle for currency of templates, update of templates on > existing languages, commit of new translations. Tasks technically the > responsibility of individual language team leaders, but in practice > needing an overseer on behalf of all languages. > > > The immediate focus is on using Pootle as the I18n framework with > > translators providing the localization. > > > > Let's divide the languages into three groups: > > > > - English (the base language) > > > > - Mediums of instruction (languages used at deployments as a common > > language where more than one language is spoken) > > > > - Local language (languages used by students at home) > > English is not always the base language of our South Amreican activity > developers, as mentioned, this requires some careful thought and > action to make these Spanish-originating activities more widely > available in other languages. > > Fortunately, the Pootle system can take the ongoing Spanish > translation of an English-originating activity and show it to > indigenous language translators (e.g. for Spanish to > Aymara/Quechua/Guarani/Awajún L10n where localizers are primarily > bilingual, but not English-speaking). Similarly, French translations > (if present in Pootle) can facilitate L10n into the indigenous > languages of Francophone Africa. This helps us create bridges to > indigenous languages by localization into a "language-of-instruc
