[Localization] How do we manage translation effort in Release, process/roadmap?

Sun Jul 6 05:18:53 EDT 2008

On Thu, Jul 3, 2008 at 4:38 AM, Greg Smith <gregsmitholpc at gmail.com> wrote:
> Hi Korakurider,
>
> Thanks for reviewing the process page.
>
> Can you write up an explanation (or point me to the URL) on the steps
> and actions needed for translation in each release? An example of what
> happens and when for new languages is helpful too. Include what
> notifications should go out as part of the steps.

I wrote up the process for new languages on the Localization Wiki
page, and used Cambodian Khmer as an example for recruiting
localizers. There is still no management process for dealing with
recruiting.

I am the Administrator for Khmer and Haitian Kreyòl, because at the
time of GiveOneGetOne there was no management process for connecting
planned deployments with the need for localization projects in the
languages of the target countries.

> If you can show agreement on the content, I can link to it from the main
> process page.
>
> Please also so suggest where in the process each piece of the
> translation work needs to happen. That wont be easy as I don't have full
> agreement on the milestones yet:
> http://wiki.laptop.org/go/Release_Process_Home#Milestones

The simple answer for software localization is, As early as possible,
well before deployment, so that there is time to develop materials for
the teachers. It is vital to have some time to discuss the creation of
computer terminology for languages that do not have it before the main
localization effort begins.

For other translation work, we don't have any visible process for
deciding what materials we want to offer. XO manuals, teacher
training, curriculum, lesson plans, textbooks, all exist in a state of
chaos, rarely in more than one language and sometimes not at all
anywhere. There are materials produced in one country that are not
available to other countries speaking the same language. We need
someone to tackle licensing for free publication and translation with
as many publishers as possible, and with schools of education and
other resource centers. I started the process with Josh Waitzkin's
book The Art of Learning by introducing Josh and his agent to Walter
Bender. I have no idea whether anybody currently at OLPC even knows
about this opportunity.

We also need to recruit people to prepare speech samples and
dictionaries for the text-to-speech engine, spelling dictionaries, and
other such materials.

> However, if you can anchor your translation steps and process on one of
> the milestones that will help. e.g. 30 days before first release
> candidate is chosen (aka Change Control of Features)"first draft of all
> translations must be entered in Pootle". Once we know what needs to
> happen we can pin it to the right place.

Start well back from there. When a country is negotiating for a
purchase, management needs to let the localization team know which
materials we want to show the purchasers well before shipment, maybe
even before the contract is signed.

> In short, tell us how you think it should be done and what you need to
> be successful. Post it to the talk page:
> http://wiki.laptop.org/go/Talk:Release_Process_Home
>
> get agreement from the key translation people doing the work and I will
> try to ensure that the development team accommodates your needs as much
>  as possible.

The development team is not the problem.

> That's a lot to ask for! Let me know if my request is not clear or if we
> should look for other people to help you get started.
>
> In my estimation, some of the best people on the project are working in
> the translation area and I really appreciate your valuable contribution.
>
> Thanks,

A pleasure, mostly.

> Greg S
>
>  Jul 2, 2008 at 12:20 AM, Korakurider <korakurider at gmail.com> wrote:
>  > > Hi, all.
>  > > I have read though Greg's release process draft of OLPC
>  > > (http://wiki.laptop.org/go/Release_Process_Home)
>  > > and ReleaseTeam/Roadmap of SugarLabs
>  > > (http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap).
>  > > But both draft documents haven't explained translation of software
>  > > (including activity) and others.
>  > >
>  > > Until midst of update.1 development, development of activities and
>  > > translation had been aligned to the road map
>  > > of XO software.  it was straightforward; we were notified when window
>  > > for translation of whole project was opened/closed.
>  > >
>  > > Now our collaboration has become complex, because of SugarLabs's split.
>  > > Translators are still working with one unified portal (i.e Pootle),

We need a separate repository for creating and translating textbooks,
manuals, lesson plans, and curricula for students and teachers.

>  > > but I can't understand how and when each PO will be pulled to build.
>  > > Without those knowledge it would be difficult for translation
>  > > community to manage their schedule.
>  > > Could you please explain about this?

Localization administrators commit the latest versions of
localizations to git when a milestone is imminent. Commits can be made
more frequently.

>  > > For instance, scheduled build of Terminal activity with pulling newer
>  > > translation was announced recently.
>  > > (http://lists.laptop.org/pipermail/localization/2008-June/001138.html)
>  > >  So we could easily manage the effort.
>  > > But could we expect similar announcement for every activities, or will
>  > > the window for translation of activity aligned to
>  > > development road map of sugarlab or OLPC?
>  > >
>  > > Maybe I missed important thing, though...
>  > >
>  > > Thanks in advance
>  > > /Korakurider
>  > > _______________________________________________
>  > > Devel mailing list
>  > > Devel at lists.laptop.org
>  > > http://lists.laptop.org/listinfo/devel
>  > >
> _______________________________________________
> Localization mailing list
> Localization at lists.laptop.org
> http://lists.laptop.org/listinfo/localization
>

-- 
Edward Cherlin
End Poverty at a Profit by teaching children business
http://www.EarthTreasury.org/
"The best way to predict the future is to invent it."--Alan Kay