Re: [l10n-dev] IMPORTANT: Translation Schedule for 2.4 - 2nd handoff
Hi Pootle users, Six languages in Pootle have just been submitted via IssueTracker and the issue numbers are: Catalan: i83973 Italian: i83116 Spanish: i83095 Khmer: i83976 Kurdish: i83974 Occitan-lengadocian: i83975 For Italian, Spanish and Khmer languages, there are still several gsicheck errors. The leaders of Italian, Spanish and Khmer communities, Can you please check the gsicheck log file on each issue, fix the errors and submit revised file by COB today? Thanks, Aijin Aijin Kim wrote: Dear Pootle users, Please note that Pootle will be down from 11/26- 29 for preparing the 2nd hand-off. Regards, Aijin Rafaella Braconi wrote: Dear Translators/Localizers, here some updates on the translation schedule as well as volume for the second and last translation round for the OpenOffice.org 2.4 Update release. All details can be found at: http://wiki.services.openoffice.org/wiki/Translation_for_2.4 Here below the highlights: Translation schedule: - final delivery deadline has been extended one week to December 20th - sdf files for translation will be available on November 29th - Pootle content will be updated November 26th to November 29th - no work on Pootle during the updating process. Translation volume for the 2nd handoff for all teams who have completed translation by November 26th: - GUI: approx. 1,200 words - Help: approx. 13,800 words Teams who jointly work on localization with Sun/Globalization are: # Dutch Community # French Community # Germanophone Community # Italian Community # Spanish Community # Brazilian Community # Swedish Community # Russian Community # Chinese Community (for Simplified Chinese) # Korean Community # Japanese Community Please let me know by Friday the volume you can commit to translate by December 20th so that I can arrange the translation work accordingly. Kind Regards, Rafaella P.S. I still have some giveaways to give you :-) . Just send an email directly to me, subject *OOo Giveaways*, indicating your name, address and language you contributed to - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] List of UI strings/translation
Hi Reiko, Reiko Saito ha scritto: Hi Rafaella, Does any of the community or translation vendor use the list of the UI messages/translation for reference ? While translating Help or UI messages, the translator will often need to confirm the existing translation. For example, in the following strings: You can view the detail by clicking Expand Tree and come back to the simple view by clicking Contract Tree. The strings Expand Tree and Contract Tree are already translated and exist in the current product, but since they are not new, the translator does not have the file including those translation, and cannot identify their translation. This will lead to inconsistent translation between UI messages and Help. Can the translator get the list of existing UI messages with translation ? The list formatted as csv, like --- Expand Tree: ツリーを展開 Contact Tree: ツリーを収縮 If those files are available, any Translation Memory Editor, e.g. OmegaT, can read the file and present them as the glossary on the tool. would a full extract of translated strings out of the GUI serve your purpose? If yes, which format would you prefer .gsi, .sdf or tmx? Thanks, Rafaella Regards, -Reiko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] List of UI strings/translation
Hi Jean-Chrisophe, Jean-Christophe Helary ha scritto: On 26 nov. 07, at 15:17, Reiko Saito wrote: Can the translator get the list of existing UI messages with translation ? The list formatted as csv, like --- Expand Tree: ツリーを展開 Contact Tree: ツリーを収縮 If those files are available, any Translation Memory Editor, e.g. OmegaT, can read the file and present them as the glossary on the tool. Rafaella, I think you mentioned a while ago (for 2.3 ?) that it was not possible to have real TMX of already existing translations. Is it still the case ? When the contents are totally new, they are not as useful but when there are incremental additions to old contents such reference files can be extremely useful and greatly easy the translation process. TMX is not required. As Reiko says, anything like CSV/TSV could be later converted to the required formats. an .sdf file can be opened and saved as CVS document... Rafaella P.S. Nice to see you back on the list! Jean-Christophe - 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]
Re: [l10n-dev] List of UI strings/translation
Hi Rafaella, Exported stgings include English and translation, right ? If so, yes that was great and perfectlly serves my purpose. I prefer CSV format, but if it is not possible, .gsi is fine. I can convert it to CSV if necessary. # .sdf and .tmx include more information than the translation. Regards, -Reiko Rafaella Braconi wrote: Hi Reiko, Reiko Saito ha scritto: Hi Rafaella, Does any of the community or translation vendor use the list of the UI messages/translation for reference ? While translating Help or UI messages, the translator will often need to confirm the existing translation. For example, in the following strings: You can view the detail by clicking Expand Tree and come back to the simple view by clicking Contract Tree. The strings Expand Tree and Contract Tree are already translated and exist in the current product, but since they are not new, the translator does not have the file including those translation, and cannot identify their translation. This will lead to inconsistent translation between UI messages and Help. Can the translator get the list of existing UI messages with translation ? The list formatted as csv, like --- Expand Tree: ツリーを展開 Contact Tree: ツリーを収縮 If those files are available, any Translation Memory Editor, e.g. OmegaT, can read the file and present them as the glossary on the tool. would a full extract of translated strings out of the GUI serve your purpose? If yes, which format would you prefer .gsi, .sdf or tmx? Thanks, Rafaella Regards, -Reiko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Reiko Saito Japanese Language Lead Translation Language and Information Services (TLIS) Globalization Services Sun Microsystems, Inc. Email: [EMAIL PROTECTED] Phone: +81 3 5962 4912 Blog: http://blogs.sun.com/reiko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] List of UI strings/translation
On 26 nov. 07, at 23:41, Rafaella Braconi wrote: Hi Jean-Chrisophe, an .sdf file can be opened and saved as CVS document... Good, as Reiko just wrote, such contents would be interesting only it it includes the English and the translation. Can you confirm it is the case ? Rafaella P.S. Nice to see you back on the list! I thought my hibernation would last longer but global warming seems to affect Japan more than what I expected ;) Jean-Christophe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Mailing list enabling
Dear Charles, Louis and other Project leaders, According to http://www.openoffice.org/scdocs/ProjectMail, it seems that the basic mailing lists (dev, cvs, announce, issues, users) for a project should be created automatically. But I can't find these at my project my.openoffice.org. How should I enable these? With Best Regards, -- Wunna Ko Ko Get Paid To Read Emails. Free To Join Now! http://www.emailcashpro.com/?source=Emailr=onlinestore
