::For coordination - we just have to have a list of files to translate and status of them such as ''translated, in progress, to translate'' see the table below. It can be done by creating progress pages (such as Translation_ru for russian language) with list of all [[applications]] and status of translation.<br>The tools and commands how to retrive files for translation and submit translated version to the appropriate destination IMO should be on the [[Translation| top of the page]] - it would not take much space.<br>Maillist for each language, where is ppl willing to work, would be very helpfull. However, since all the translators able to read and write in english - we can use regular maillist for developers, or just one dedicated maillist for all translators.<br> Also I doubt nessesity to split wiki on language basis at present time.<br>[[User:Dmitri|Dmitri]] 09:03, 23 February 2007 (CET)

::For coordination - we just have to have a list of files to translate and status of them such as ''translated, in progress, to translate'' see the table below. It can be done by creating progress pages (such as Translation_ru for russian language) with list of all [[applications]] and status of translation.<br>The tools and commands how to retrive files for translation and submit translated version to the appropriate destination IMO should be on the [[Translation| top of the page]] - it would not take much space.<br>Maillist for each language, where is ppl willing to work, would be very helpfull. However, since all the translators able to read and write in english - we can use regular maillist for developers, or just one dedicated maillist for all translators.<br> Also I doubt nessesity to split wiki on language basis at present time.<br>[[User:Dmitri|Dmitri]] 09:03, 23 February 2007 (CET)

::: As i posted on the community mailinglist i think we *really* need a translatoin mailing list (if not one for every language) , i aggree with the abovementined need for a coordinator too even if not so necessery IMHO. '''join the discussion [http://lists.openmoko.org/pipermail/community/2007-April/004973.html OM-i18n-ml] on the community mailinglist.''' [[User:Cga|cga]] sat apr 28th 20:24:38 CEST 2007

::: As i posted on the community mailinglist i think we *really* need a translatoin mailing list (if not one for every language) , i aggree with the abovementined need for a coordinator too even if not so necessery IMHO. '''join the discussion [http://lists.openmoko.org/pipermail/community/2007-April/004973.html OM-i18n-ml] on the community mailinglist.''' [[User:Cga|cga]] sat apr 28th 20:24:38 CEST 2007

+

:: Hi all, I read the discussion on the ML (just subscribed so I will bring up the discussion there). I think a ML is needed for each language and even a coordinator is needed, one who is responsible for checking the translations and (maybe) to upload them via SVN. I think the ML would be of great use even for reviewing translations (IMHO we have to have a really high standard for translations). --[[User:Milo|Milo]] 10:50, 12 July 2007 (CEST)

Example for pages with translation status

Contacts

Calendar

Need for translation mailing list (and coordinators?)

Who is coordinating translation, in paticular, russian one? I would be nice to see the progress and where is newcomers can fit in. Dmitri 05:33, 23 February 2007 (CET)

There is already main SVN which probably will contain all the translations (I think it is no problem for OpenMoko team). I propose to create mailing list for translators (like Debian's debian-l10n-russian@ list), and wiki page "how to start translating", with the name of coordinator (do you want to be the coordinator? ;), mailing list name, translation rules and so on. MikhailGusarov 07:42, 23 February 2007 (CET)

For coordination - we just have to have a list of files to translate and status of them such as translated, in progress, to translate see the table below. It can be done by creating progress pages (such as Translation_ru for russian language) with list of all applications and status of translation.The tools and commands how to retrive files for translation and submit translated version to the appropriate destination IMO should be on the top of the page - it would not take much space.Maillist for each language, where is ppl willing to work, would be very helpfull. However, since all the translators able to read and write in english - we can use regular maillist for developers, or just one dedicated maillist for all translators. Also I doubt nessesity to split wiki on language basis at present time.Dmitri 09:03, 23 February 2007 (CET)

As i posted on the community mailinglist i think we *really* need a translatoin mailing list (if not one for every language) , i aggree with the abovementined need for a coordinator too even if not so necessery IMHO. join the discussion OM-i18n-ml on the community mailinglist.cga sat apr 28th 20:24:38 CEST 2007

Hi all, I read the discussion on the ML (just subscribed so I will bring up the discussion there). I think a ML is needed for each language and even a coordinator is needed, one who is responsible for checking the translations and (maybe) to upload them via SVN. I think the ML would be of great use even for reviewing translations (IMHO we have to have a really high standard for translations). --Milo 10:50, 12 July 2007 (CEST)

Example for pages with translation status

Contacts

Calendar

Need for translation mailing list (and coordinators?)

Who is coordinating translation, in paticular, russian one? I would be nice to see the progress and where is newcomers can fit in. Dmitri 05:33, 23 February 2007 (CET)

There is already main SVN which probably will contain all the translations (I think it is no problem for OpenMoko team). I propose to create mailing list for translators (like Debian's debian-l10n-russian@ list), and wiki page "how to start translating", with the name of coordinator (do you want to be the coordinator? ;), mailing list name, translation rules and so on. MikhailGusarov 07:42, 23 February 2007 (CET)

For coordination - we just have to have a list of files to translate and status of them such as translated, in progress, to translate see the table below. It can be done by creating progress pages (such as Translation_ru for russian language) with list of all applications and status of translation.The tools and commands how to retrive files for translation and submit translated version to the appropriate destination IMO should be on the top of the page - it would not take much space.Maillist for each language, where is ppl willing to work, would be very helpfull. However, since all the translators able to read and write in english - we can use regular maillist for developers, or just one dedicated maillist for all translators. Also I doubt nessesity to split wiki on language basis at present time.Dmitri 09:03, 23 February 2007 (CET)

As i posted on the community mailinglist i think we *really* need a translatoin mailing list (if not one for every language) , i aggree with the abovementined need for a coordinator too even if not so necessery IMHO. join the discussion OM-i18n-ml on the community mailinglist.cga sat apr 28th 20:24:38 CEST 2007