Talk:Translation

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Rosetta is a nice tool)
(Suggestion- Software for translating)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Who is coordinating translation, in paticular, russian one? I would be nice to see the progress and where is newcomers can fit in. [[User:Dmitri|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 <code>debian-l10n-russian@</code> 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. [[User:MikhailGusarov|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.<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)
 
 
==Translation status==
 
==Translation status==
 
one master "skeleton" page with all the [[applications]] preformatted in tables and initial status ''to translate'', and one page per language with progress status based on the master page:
 
one master "skeleton" page with all the [[applications]] preformatted in tables and initial status ''to translate'', and one page per language with progress status based on the master page:
  
Example/Skeleton of the translation table
 
 
==Example for Skeleton translation table==
 
==Example for Skeleton translation table==
 +
 
===Contacts===
 
===Contacts===
 
{|
 
{|
Line 75: Line 72:
 
|}
 
|}
 
|}
 
|}
 +
 +
== 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. [[User:Dmitri|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 <code>debian-l10n-russian@</code> 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. [[User:MikhailGusarov|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.<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
 +
:: 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)
  
 
== Rosetta is a nice tool ==
 
== Rosetta is a nice tool ==
Line 85: Line 89:
  
 
* Rosetta could be nice but is closed source. if i was "you" I'd try to be as open as possible. there are good software already for po* files. but hey.. you are free to do what you want =)
 
* Rosetta could be nice but is closed source. if i was "you" I'd try to be as open as possible. there are good software already for po* files. but hey.. you are free to do what you want =)
 +
 +
* Rosetta is really nice, I use it almost every day for Ubuntu. There are some external projects that use it... but it's closed source, even if it's a nice app. Anyway, IMHO developers or project coordinators should choose if a move to Launchpad is necessary. --[[User:Milo|Milo]] 10:54, 12 July 2007 (CEST)
 +
 +
 +
== Pootle ==
 +
 +
There is also Pootle. According to its features( http://translate.sourceforge.net/wiki/pootle/features ) it might be really useful in OpenMoko translation, it's possible  to use it for offline and online editing,  it can show those fancy color graphs (translated/untranslated/fuzzy),there is  Subversion integration, permission system, local installation etc. --[[User:Vatoz|Vatoz]] 17:59, 2 January 2008 (CET)

Latest revision as of 17:59, 2 January 2008

Contents

[edit] Translation status

one master "skeleton" page with all the applications preformatted in tables and initial status to translate, and one page per language with progress status based on the master page:

[edit] Example for Skeleton translation table

[edit] Contacts

Contacts
file1 to translate
file2 to translate
file3 to translate

[edit] Calendar

Calendar
file4 to translate
file5 to translate
file6 to translate

[edit] Example for pages with translation status

[edit] Contacts

Contacts
file1 to translate
file2 In progress since yyyy-mm-dd
file3 translated yyyy-mm-dd

[edit] Calendar

Calendar
file4 to translate
file5 to translate
file6 to translate

[edit] 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)

[edit] Rosetta is a nice tool

I use Rosetta when I'm translating programs in Ubuntu. It works very good. Maybe we could use that, or be inspired by that. https://translations.launchpad.net/ Try looking in the page given. EsbenDamgaard 14:50, 21 March 2007 (CET)

  • Rosetta could be nice but is closed source. if i was "you" I'd try to be as open as possible. there are good software already for po* files. but hey.. you are free to do what you want =)
  • Rosetta is really nice, I use it almost every day for Ubuntu. There are some external projects that use it... but it's closed source, even if it's a nice app. Anyway, IMHO developers or project coordinators should choose if a move to Launchpad is necessary. --Milo 10:54, 12 July 2007 (CEST)


[edit] Pootle

There is also Pootle. According to its features( http://translate.sourceforge.net/wiki/pootle/features ) it might be really useful in OpenMoko translation, it's possible to use it for offline and online editing, it can show those fancy color graphs (translated/untranslated/fuzzy),there is Subversion integration, permission system, local installation etc. --Vatoz 17:59, 2 January 2008 (CET)

Personal tools

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)

Translation status

one master "skeleton" page with all the applications preformatted in tables and initial status to translate, and one page per language with progress status based on the master page:

Example/Skeleton of the translation table

Example for Skeleton translation table

Contacts

Contacts
file1 to translate
file2 to translate
file3 to translate

Calendar

Calendar
file4 to translate
file5 to translate
file6 to translate

Example for pages with translation status

Contacts

Contacts
file1 to translate
file2 In progress since yyyy-mm-dd
file3 translated yyyy-mm-dd

Calendar

Calendar
file4 to translate
file5 to translate
file6 to translate

Rosetta is a nice tool

I use Rosetta when I'm translating programs in Ubuntu. It works very good. Maybe we could use that, or be inspired by that. https://translations.launchpad.net/ Try looking in the page given. EsbenDamgaard 14:50, 21 March 2007 (CET)

  • Rosetta could be nice but is closed source. if i was "you" I'd try to be as open as possible. there are good software already for po* files. but hey.. you are free to do what you want =)