Re: [l10n-dev] Translation Schedule for 2.3
Hi, I'm the team leader for the Kinyarwanda OpenOffice translation. Unfortunately we missed out on previous versions due to missing vital steps in the procedure, so are keen to keep up to date this time. Is any action needed by us before July 26th for our language to be included, and is it still correct to be translating the latest SRC680 po files (currently SRC680_m214)? Many regards, Steve. --- Rafaella Braconi [EMAIL PROTECTED] wrote: Dear Translators/Localizers, I would like to give you some information about the upcoming 2.3 update release. Translation deadline for 2.3 is July 26th, 2007 We estimate that the wordcount to be translated for the 2.3 update release to be approx. 3000 for the GUI and 17,000 for the Help. Note that July 26th is also the bug fixing deadline for all language relevant issues. After this deadline only very critical l10n bugs will be fixed. Release Map with translation deadlines specific for the 2.3 release can be found at: http://wiki.services.openoffice.org/wiki/OOoRelease23 For this release following languages/teams will be translating using the Pootle Server we recently set up on the virtuallab: Italian, Khmer, Russian The Sun/Globalization team (in a few cases in collaboration with some N-L communities) will be working on the below languages: French, Italian, German, Swedish, Spanish, Brazilian Portuguese, Dutch, Chinese Simplified, Chinese Traditional, Korean, Japanese, Hungarian, Polish However, if you wish to contribute to the translation work for the above listed languages - as some of the native language team did for last release - just drop me an email specifying the volume you will be able to translate by June 4th. The Chinese OOo native language team will be translating the complete update release. In case of collaboration work between Sun and N-L teams, the translation schedule will be: 1st handoff delivery from Sun (for the above languages)- June 5th/6th delivery to Sun: July 5th The volume - based on actual wordcounts (that may vary a bit) is: Help: 15,000 GUI: 3,000 2nd and final handoff: delivery from Sun (for the above langauges): July 12th delivery to Sun: July 26th The volume of this second handoff will be estimated at the beginning of July. The process to follow will be: - Sun creates issues and attaches .sdf files to translate (volume to be decided by each Community based on their availability and resources) - Issues will be assigned to the translation Community leads - Community converts into po files (if any problem with that we will take over conversion) - Community translates the files using a translation .po editor - Community back converts the .po files into .sdf - Community runs gsicheck on sdf and delivers back to Sun - Sun will import the translated files into 2.3 - Sun will carry our linguistic review on translated files - Community will implement linguistic review results into translated files and deliver updated files no later than UI and feature freeze date for 2.4 release. Hope this information is useful for you to schedule your work. Kind Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Translation Schedule for 2.3
Hi Stephen, Stephen Holt wrote: Hi, I'm the team leader for the Kinyarwanda OpenOffice translation. Unfortunately we missed out on previous versions due to missing vital steps in the procedure, so are keen to keep up to date this time. Great to hear that! Is any action needed by us before July 26th for our language to be included, and is it still correct to be translating the latest SRC680 po files (currently SRC680_m214)? Currently this is the lastest file but not the last one to complete the transaltion for 2.3. You will need to update the translated files with the following milestones and then deliver the translated files (note that you'll need to have at least 80% of translated GUI) attaching them to an issue. Just watch for Vadimir's or Ivo's announcement on how to deliver translated files. Regards, Rafaella Many regards, Steve. --- Rafaella Braconi [EMAIL PROTECTED] wrote: Dear Translators/Localizers, I would like to give you some information about the upcoming 2.3 update release. Translation deadline for 2.3 is July 26th, 2007 We estimate that the wordcount to be translated for the 2.3 update release to be approx. 3000 for the GUI and 17,000 for the Help. Note that July 26th is also the bug fixing deadline for all language relevant issues. After this deadline only very critical l10n bugs will be fixed. Release Map with translation deadlines specific for the 2.3 release can be found at: http://wiki.services.openoffice.org/wiki/OOoRelease23 For this release following languages/teams will be translating using the Pootle Server we recently set up on the virtuallab: Italian, Khmer, Russian The Sun/Globalization team (in a few cases in collaboration with some N-L communities) will be working on the below languages: French, Italian, German, Swedish, Spanish, Brazilian Portuguese, Dutch, Chinese Simplified, Chinese Traditional, Korean, Japanese, Hungarian, Polish However, if you wish to contribute to the translation work for the above listed languages - as some of the native language team did for last release - just drop me an email specifying the volume you will be able to translate by June 4th. The Chinese OOo native language team will be translating the complete update release. In case of collaboration work between Sun and N-L teams, the translation schedule will be: 1st handoff delivery from Sun (for the above languages)- June 5th/6th delivery to Sun: July 5th The volume - based on actual wordcounts (that may vary a bit) is: Help: 15,000 GUI: 3,000 2nd and final handoff: delivery from Sun (for the above langauges): July 12th delivery to Sun: July 26th The volume of this second handoff will be estimated at the beginning of July. The process to follow will be: - Sun creates issues and attaches .sdf files to translate (volume to be decided by each Community based on their availability and resources) - Issues will be assigned to the translation Community leads - Community converts into po files (if any problem with that we will take over conversion) - Community translates the files using a translation .po editor - Community back converts the .po files into .sdf - Community runs gsicheck on sdf and delivers back to Sun - Sun will import the translated files into 2.3 - Sun will carry our linguistic review on translated files - Community will implement linguistic review results into translated files and deliver updated files no later than UI and feature freeze date for 2.4 release. Hope this information is useful for you to schedule your work. Kind Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] TM, glossaries and OmegaT
On 11 juin 07, at 22:07, Rafaella Braconi wrote: Hi Alexandro, for Russian Italian and Khmer we are referring to the Pootle server hosted on the Sun virtuallab. Please see details at: http://wiki.services.openoffice.org/wiki/New_Translation_Process_% 28Pootle_server%29 The 3 above languages are the only one which will be using Pootle to translate the 2.3 version since we are in the initial/pilot phase. If everything goes well or at least we sort our the issues and we are able to fix them, all other languages and team that want to be added to this tool are more than welcome to join. That would be for the 2.4 release. If non-pootle users still want to use TMs it is possible to use OmegaT too. Sun can probably provide us with TMX files of previous translations in the relevant language pairs, the SunGloss contents can be exported as a glossary file and the source PO can be pretty much translated as is. The correct procedure would be: 0) create a project in OmegaT 1) correctly format the PO file with msgcat 2) put that file in /source/ 3) make sure that your TMX has srclang set to your source language the way it was defined in the project settings 4) put the TMX file in /tm/ 5) make sure the exported SunGloss is a tab separated list in at most 3 columns (1st col= source language, 2nd col=target lang, 3rd col= comments) 6) put the glossary in /glossary/ 7) open the project and translate 8) when the translation is completed, msgcat the file in /target/ and deliver For info, OmegaT is a GPLed Java Computer Aided Translation tool developed for _translators_. It is specifically _not_ for geeks. Which means that it is relatively straight forward to use. I am pretty sure the filters can be tweaked to directly support the .sdf format but I leave that to others. I know some already use it here. NetBeans localizers also use it intensively. And real translators too :) Jean-Christophe Helary (OOo-fr) http://sourceforge.net/projects/omegat/ CVS veersion: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/ omegat co -P omegat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
