Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Op Do, 2010-06-24 om 10:50 +0200 skryf Goran Rakic: У чет, 24. 06 2010. у 08:13 +0200, André Schnabel пише: Did anybody try to build a tmx from old translations using po2tmx and then pretranslate? If I clear all duplicates in my compendium I have 100% fuzzy match with PO too. Fuzzy match is not the same as moving the exact translation string. Moving translation string does not require any review. I completely agree that matching strings by identifier is more valuable than a 100% string match. = Contexts everywhere = oo2xliff gives you the full context ;) This is a missing feature in oo2po. Context is passed and visible in a comment, not in a gettext msgctxt field where other tools expects it. The msgctxt field was always meant to be used to disambiguate otherwise identical messages. It isn't meant to be an identifier for the string, because the source text (msgid) is the unique identifier (when combined with the optional msgctxt). When we added support for msgctxt in the converters, the support for it in many PO software was very minimal, so we obviously wanted to only use it where it was necessary (and we continued to give alternatives, such as KDE comments, merging, etc.) Recent releases of the toolkit (since version 1.3.0) only support merge and msgctxt, however. Maybe we should add an option to always add msgctxt based on the identifier, similar to the old msgid_comment_all style we used to have: http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle using tmx gives you what you want. Iv you use xliff as format for translation files, you could even correctly mark how the segment was translated and decide later hwo to deal with such segments (auto-approve, review ...) I can do the same with PO file. Maybe the semantics is not standardized like in xliff but xliff is overcomplicated. I want to be able to grep and sed my translations, I can not do that with xliff. Just in case some people weren't aware: pogrep from the Translate Toolkit can search in XLIFF, PO and TMX files (and even .mo files as well :-) http://translate.sourceforge.net/wiki/toolkit/pogrep Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Frank Mau, is it possible to restore the CUI module? 24.06.2010 22:33, Serg Bormant пишет: Hi, 2010/6/23 Frank Maufrank@sun.com: Ok, restored module CUI for all languages (if available). As I can see, you used at least before 3.2.0 translation for Russian CUI module (for ex. #: align.src#RID_SVXPAGE_ALIGNMENT.BTN_ASIAN_VERTICAL.tristatebox.text msgid Asian layout ~mode corrected in 3.2.0 to fit Calc cell properties dialog box). Can you please restore CUI Russian module to previous state? Can you guarantee the absence of similar problems in other translations? - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, I'm not Friedel, but ... ;) Am 24.06.2010 01:33, schrieb Goran Rakic: What I see as missing from pomigrate2 is that PO catalogs should be actually read on migration, relaying just on filenames is not reliable enough. Did anybody try to build a tmx from old translations using po2tmx and then pretranslate? I did it yesterday an all the moved strings got translated. Only problem in XLIFF is, that pretranslate adds the strings as suggestion, not as translation (It was much better for XLIFF to add as translation and mark as 100% match). = Contexts everywhere = oo2xliff gives you the full context ;) = Merge reading all catalogs = using tmx gives you what you want. Iv you use xliff as format for translation files, you could even correctly mark how the segment was translated and decide later hwo to deal with such segments (auto-approve, review ...) *sigh* it's like battling against thousands of tools that process binary .doc files where you could have a small number of better tools that can easily process odf, because it is xml. Regards, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Am 23.06.2010 19:45, schrieb André Schnabel: Hi, Am 23.06.2010 18:44, schrieb Frank Mau: Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. any chance to get it for German as well? .. if it is to complicated, I'll wait for the TMX. Ok, I built my tmx yesterday - and get automatic translation for the moved strings. So, I can handle the issue. Thanks, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Sokhem, On 24.06.10 03:09, Khoem Sokhem wrote: On Tuesday 22 June 2010 11:29:29 ព្រឹក Khoem Sokhem បានសរសេរ ៖ Hello, I saw the file in .../devel/DEV300/DEV300_m83/Build-1/POT/ only 1KB of size. I think it is not a valid POT file for translating. Could the file be located other location beside the a bove location? Where can I get DEV300_m83 for UI translating for Beta release ? Instructions where to find source English US sdf can be found at: http://wiki.services.openoffice.org/wiki/Translation:General_Information#en_US_Source_Strings Please note that m83 is not yet the milestone for the Beta release, but it's worth while starting with the translation and update it incrementally. Thanks, Rafaella
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
У чет, 24. 06 2010. у 08:13 +0200, André Schnabel пише: Did anybody try to build a tmx from old translations using po2tmx and then pretranslate? If I clear all duplicates in my compendium I have 100% fuzzy match with PO too. Fuzzy match is not the same as moving the exact translation string. Moving translation string does not require any review. = Contexts everywhere = oo2xliff gives you the full context ;) This is a missing feature in oo2po. Context is passed and visible in a comment, not in a gettext msgctxt field where other tools expects it. using tmx gives you what you want. Iv you use xliff as format for translation files, you could even correctly mark how the segment was translated and decide later hwo to deal with such segments (auto-approve, review ...) I can do the same with PO file. Maybe the semantics is not standardized like in xliff but xliff is overcomplicated. I want to be able to grep and sed my translations, I can not do that with xliff. Goran - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Rafaella, Hi Frank Thank you very much for your kind attention to the issue. Best regards, Olivier Em 23-06-2010 14:21, Rafaella Braconi escreveu: This is great news! Thank you Frank for all your work! @ all Pootle Users: as Frank has said, the previous translations have been restored. You can now proceed with the translation work. Kind Regards, Rafaella Frank Mau ha scritto: Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. Cheers, Frank Rafaella Braconi schrieb: Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org -- Olivier Hallot OpenOffice.org L10n Leader for Brazilian Portuguese Rio de Janeiro - Brasil - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, 2010/6/23 Frank Mau frank@sun.com: Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. You comletely trash my work on CUI. Big thanks. But why? -- wbr, sb - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, 2010/6/23 Frank Mau frank@sun.com: Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. I merged Rrussian translation from previous release to CUI before your intrusion, so 6008 translated, 0 fuzzy, 27 untranslated (really new). And now I can see 5970 untarnslated, 25 fuzzy, 40 untarnslated. So, you comletely trash my work on CUI. Big thanks. But why? -- wbr, sb - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Frank, what source was used for restoring CUI? As I can see it has many, many bugs in Russian translation, for ex. msgid SQL Syntax Highlighting msgstr Подсветка синтаксиса SGML You can see, that SQL and SGML too different to be used as 100% equivalent, but this record has no fuzzy mark 8( I don'n know about other surprises. But I cannot trust the method used :-( -- wbr, sb - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, 2010/6/23 Frank Mau frank@sun.com: Ok, restored module CUI for all languages (if available). As I can see, you used at least before 3.2.0 translation for Russian CUI module (for ex. #: align.src#RID_SVXPAGE_ALIGNMENT.BTN_ASIAN_VERTICAL.tristatebox.text msgid Asian layout ~mode corrected in 3.2.0 to fit Calc cell properties dialog box). Can you please restore CUI Russian module to previous state? Can you guarantee the absence of similar problems in other translations? -- wbr, sb - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Op Di, 2010-06-22 om 14:42 +0200 skryf Rafaella Braconi: Hi Olivier, Hi everybody On 22.06.10 11:59, Olivier Hallot wrote: Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx32/ In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... I am surprised to hear that the PO files aren't in version control - it has many advantages, so I would strongly recommend it. Translation memory in Pootle will solve some of the issues we are talking about, but I still believe we need a way to find specific versions of the translations reliably. The upcoming version of Pootle has made good progress towards giving translation memory in the online translation interface. Although the final bits aren't implemented yet, I hope we can have it reasonably soon. I'd really appreciate it if people can get involved - at least for working towards a user interface for it. For the case of OOo (especially if stuff moved around), I think using TMX files during the upgrade and/or pomigrate2 is still the better solution anyway, since a cleaner migration to a new version means less review work, whereas translation memory would mean more information for translators, but requiring lots of review. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Op Wo, 2010-06-23 om 07:55 +0200 skryf André Schnabel: Hi, Hallo Goran, André, everybody. Am 22.06.2010 21:39, schrieb Goran Rakic: У уто, 22. 06 2010. у 16:10 -0300, Olivier Hallot пише: Hi Rafaella dev's I would like to express my deep disapointment with this situation. I will second that, but for what I know the problem here is in our PO toolkit, not in the process how developers work. Things can easily improve by creating a new tool for merging POTs created from SDF file with old PO files that could cope up with code moving from one module into another. If there are no voices against it I can work on this during July so we can test and improve it later and make it ready for next release cycle. Hmm .. I'm not really keen of having yet another tool. If we are working on something, this should be done within translate toolkit. The pretranslate tool from translate toolkit is supposed to do exactly what we need - unfortunately it doesn't work the way we need it. The tool that Goran mentions, pomigrate2 is supposed to handle this to some extent. Goran, can you maybe help us see what is currently missing in pomigrate2 to handle this situation? We should file a bug for the Translate Toolkit to ensure that we can prioritise this and try to fix this for everyone's benefit. At least not for xliff - did anybody try with .po? I also did not check, how successfull pretranslate works with translation memories. Unfortunately pretranslate manpage gives no information, what format to use as translation memory file. In fact - for my own workflow (using xliff files, OLTE and built in translation memory which is based on the translations I did so far) gives ~ 60% automatic transaltions for the moved strings. My translatoin memory does not contain all the previus translations, therefore the rather low rate. Unfortunately there is no german tmx file at ooo.services :( So for me - before starting a new tool I'd recommend: - to provide .tmx files based on previous translations for all languages - try to improve translate toolkit - teach developers about the workload some acitivities cause here, that seem to be very simple for developers and find some way to move l10n strings along with the original english strings I agree with all of this. Several tools, such as our own Virtaal, can use the TMX file to provide speedup to translators when working. We shouldn't underestimate the difference in value between identifier matched TM, and source text matched TM - matching perfectly on identifier and source text is the first prise, and would mean that no review of the string would be necessary (in principle). Matching on source text only (as you would with TMX files) would need review, in my opinion (at least for anything shorter). So please, let us work together to fix whatever we need on the tools side (including for teams using XLIFF :-) - We need to migrate translations well if source code moves, without translators needing to do a lot of work. I believe pomigrate2 is at least a step in the right direction, maybe with some outstanding work. - We need to ensure that up-to-date translation memories are available for people to use (regardless of whether source code moves or not). Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Valter, Valter Mura ha scritto: In data martedì 22 giugno 2010 14:42:35, Rafaella Braconi ha scritto: Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localizati on/tmx32/ I do confirm, with regret, I cannot found an updated tmx for Italian... me neither. Let me check and come back to you. Rafaella Ciao - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Friedel et al., good to know you're making progress in version 2.x. Btw. we ordered a new Pootle server for the OO.o community so we can get rid of the old infrastructure. We may need your help Friedel to set up a Pootle 2.x on the machine (and yes with a Linux ;-) ). That's the good news the bad one is, we won't have this server in place for the current 3.3 translation round, sorry. Cheers, Frank F Wolff schrieb: Op Di, 2010-06-22 om 14:42 +0200 skryf Rafaella Braconi: Hi Olivier, Hi everybody On 22.06.10 11:59, Olivier Hallot wrote: Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx32/ In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... I am surprised to hear that the PO files aren't in version control - it has many advantages, so I would strongly recommend it. Translation memory in Pootle will solve some of the issues we are talking about, but I still believe we need a way to find specific versions of the translations reliably. The upcoming version of Pootle has made good progress towards giving translation memory in the online translation interface. Although the final bits aren't implemented yet, I hope we can have it reasonably soon. I'd really appreciate it if people can get involved - at least for working towards a user interface for it. For the case of OOo (especially if stuff moved around), I think using TMX files during the upgrade and/or pomigrate2 is still the better solution anyway, since a cleaner migration to a new version means less review work, whereas translation memory would mean more information for translators, but requiring lots of review. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
In data mercoledì 23 giugno 2010 01:00:16, Valter Mura ha scritto: In data martedì 22 giugno 2010 14:42:35, Rafaella Braconi ha scritto: Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/lo calizati on/tmx32/ I do confirm, with regret, I cannot found an updated tmx for Italian... Ciao There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Paolo - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Olivier, Hi Rafaella dev's I would like to express my deep disapointment with this situation. I just can't figure why we, translators, have to fix code refactoring l10n issues, without any early notice and with apparently not a miminal concern from the developers with respect to the overload they inflict to us. Our job is not a lesser job, and we produce what our NL users see first-hand in the software. I am not concerned on re-work thru automatic cut--paste on something already done long time ago. I am concerned on the error and mistakes we will for sure introduce each time we have to edit a po file that has been committed years before, with almost no backup or easy traceback procedure to recover the precise string used at that time. As said in this thread, it is the same workload as if it was new. So, I beg you to work on how to stop this. I am fully with you and I'll make sure this will be handled with priority. Also, please note that Frank is restoring the status of the CUI module by using the previous translations. It's taking some time since this is a manual work. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Kind Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Now I am furious, I have a fully localized m83 and now I will have to - what? Lp, m. 2010/6/23 Rafaella Braconi rafaella.brac...@sun.com Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Haha, OK, great! Lp, m. 2010/6/23 Rafaella Braconi rafaella.brac...@sun.com Hi Martin Martin Srebotnjak ha scritto: Now I am furious, I have a fully localized m83 and now I will have to - what? sorry I was not clear. This refers to the ones translating with Pootle. Glad to be far away from furious translators ;-) . Rafaella Lp, m. 2010/6/23 Rafaella Braconi rafaella.brac...@sun.com Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Martin Martin Srebotnjak ha scritto: Now I am furious, I have a fully localized m83 and now I will have to - what? sorry I was not clear. This refers to the ones translating with Pootle. Glad to be far away from furious translators ;-) . Rafaella Lp, m. 2010/6/23 Rafaella Braconi rafaella.brac...@sun.com Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. Cheers, Frank Rafaella Braconi schrieb: Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
This is great news! Thank you Frank for all your work! @ all Pootle Users: as Frank has said, the previous translations have been restored. You can now proceed with the translation work. Kind Regards, Rafaella Frank Mau ha scritto: Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. Cheers, Frank Rafaella Braconi schrieb: Hi Paolo, All, There is no need to provide them for italian, I created by myself using 3.2.1 translations and made it available to translators. Of course having them in an official repository would be better, but it not a big issue.. Frank just told me that he will be providing the OOo 3.2.1 tmx files. Also, he is restoring the status of the CUI module by using the previous translations. So please stay tuned and wait till the status of the http://pootle.sunvirtuallab.com/xx/openoffice_org/cui folder is restored. This applies to all languages. Thanks, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
In data mercoledì 23 giugno 2010 19:21:14, Rafaella Braconi ha scritto: This is great news! Thank you Frank for all your work! @ all Pootle Users: as Frank has said, the previous translations have been restored. You can now proceed with the translation work. Kind Regards, Rafaella Thanks for the info, regards, -- Valter Registered Linux User #466410 http://counter.li.org Kubuntu Linux: www.kubuntu.org OpenOffice: www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Am 23.06.2010 18:44, schrieb Frank Mau: Ok, restored module CUI for all languages (if available). TMX files comes tomorrow. any chance to get it for German as well? .. if it is to complicated, I'll wait for the TMX. Thanks, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
У сре, 23. 06 2010. у 10:04 +0200, F Wolff пише: Hmm .. I'm not really keen of having yet another tool. If we are working on something, this should be done within translate toolkit. The tool that Goran mentions, pomigrate2 is supposed to handle this to some extent. Goran, can you maybe help us see what is currently missing in pomigrate2 to handle this situation? Hi Friedel, all Thank you for your comments. I do not know a lot about translate toolkit source, so please forgive me if I say something wrong here. What I would like it to have your feedback on some ideas and this may lead to a better work flow or better tools. I should say that I am very happy to be able to use Translate toolkit. It helps me a lot to create better translations for OpenOffice.org, as I am sure it helps many others. What I see as missing from pomigrate2 is that PO catalogs should be actually read on migration, relaying just on filenames is not reliable enough. I think about OpenOffice.org as a single gettext domain. This split to many PO files that we have is to help us managing translations but these files are not different domains. In KDE or GNOME you do not get string moved from the Minesweeper game to the email client between releases while in OpenOffice.org it is easy to have string moved between modules. Using pomigrate2 with compendium option enabled is close to what I would like and I can usually get better result when using it but using compendium with the current from POT files as generated by oo2po is not the same as moving as messages are merged together. I want to apply compendium after the messages are moved to get fuzzy matching against new strings, but I would like to have existing translation simply moved between files. As pomigrate2 relies on filenames it also can give a huge bloat. When testautmation was included in the m83 SDF by mistake we got a new UI.po file in the testautomation directory with 3 new messages. pomigrate2 found a large UI.po file in the source three and copied hundreds of messages kept as deprecated translation memory. Three new messages where actually left as untranslated. :) = Contexts everywhere = First I would like if oo2po could provide msgctxt field to all messages and not just for duplicates inside a single PO file. Resource IDs that could be found in the SDF file are exactly what gettext context field is designed for. I know that this will create a lot of repetitive messages but we all learned long ago that every string should have its context. Different languages make distinction between noun and verb or have rich morphology and require different word forms for different adjective case etc. Translators can always auto apply translation memory to quickly translate same messages with different contexts and poconflicts can be used to check if message is translated differently while it should not be. I believe there is no any drawback from using contexts with all messages. = Merge reading all catalogs = Having msgctxt/msgid, a smarter pomigrate2 could just look for a exact match when merging translations with new POT files. This could be implemented either by building a compendium and asking msgmerge to do it or having a smarter dedicated code traversing every message from new templates. Removed messages could be kept as deprecated translation memory in the most probably file (same if it exists, in the file where most of the messages are moved or, finally, in the file with the most similar filename). Now if for any reason resource ID changes we will always have good fuzzy matching working on that string. I did not do any tests but I strongly believe this will keep all translations when messages are moved and resource ID stay the same and still provide a good fuzzy match if resource ID changes. = Some unrelated comments = I wrote a wrapper around msgmerge to add --previous flag when called from pomigrate2. That is very useful option of msgmerge when reviewing fuzzy matches. I like even more ediff output style as provided by Pology[1] (run posieve diff-previous lang.po after msgmerge --previous) but that can be handled later by editors. When using version control (we are using Subversion repository for Serbian OpenOffice.org translations) pomerge from translate toolkit makes a mess. It outputs all messages, not just a modified ones making version control diffs hard to comprehend. I like the speed of pogrep and the power of pofilter but for merging correction back I use Pology and posieve with merge_corr_tree sieve. (with pogrep output in ui-check run posieve merge_corr_tree ui -spathdelta:ui:ui-check to merge fixes). It goes over all catalogs in the ui three, looking for same in the ui-check three and updates only modified messages keeping very nice diffs. It would be great to have pomerge doing the same. Best regards, Goran Rakic [1]
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
On Tuesday 22 June 2010 11:29:29 ព្រឹក Khoem Sokhem បានសរសេរ ៖ Hello, I saw the file in .../devel/DEV300/DEV300_m83/Build-1/POT/ only 1KB of size. I think it is not a valid POT file for translating. Could the file be located other location beside the a bove location? Where can I get DEV300_m83 for UI translating for Beta release ? Thank for your response. Sokhem - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Olivier, On 21.06.10 21:48, Olivier Hallot wrote: Hi Rafaella Is Pootle already loaded with the new strings? yes, it has been updated with milestone 83. Because I had a glimpse at the pt-BR strings and had a bad feeling that several files were reset to zero translation, Are you talking about Help or UI strings? Can you provide some examples so that we can try to verify? Thanks, rafaella or there is a shuffling among them and no track on what have changed. Also, looking at the feature freeze page, it seems to me that we should not have that much to translate. Thanks Regards Em 21-06-2010 13:42, Rafaella Braconi escreveu: Hi André, André Schnabel ha scritto: Hi, Am 21.06.2010 18:13, schrieb Rafaella Braconi: Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches hmm but this would mean, that second handover will bring almost no more new strings in? Can you confirm this? With the m83 almost all changes - especially in the Help - have already been integrated. With the second handoff there will be some additional changes, but at the moment I don't have any estimates about their volume. As soon as I have any updates, I'll let you know. In the meanwhile, I would encourage all the teams to use this time to translate before the second handoff. Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org -- Rafaella Braconi Program Manager Nagelsweg 55 D-20097 Hamburg Phone: +49-40-23646-0 Email: rafaella.brac...@sun.com Sitz der Gesellschaft: Sun Microsystems GmbH Sonnenallee 1, D-85551, Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Jürgen Kunz - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Martin, On 22.06.10 00:17, Martin Srebotnjak wrote: Rafaella, I am singlehandedly working on the Slovenian translation and have my own localization server. I have regularly updated my files so yesterday I had just one fuzzy string left with the updated m83. If I understand you correctly, even if I am not working via Pootle, I have to send the sdf to you (or add it to an issue) before July 1, so that you get a almost-fully-translated stuff for all languages into the tree and then update my files after July 1? Or do I keep updating to new m84, m85 etc. until OOO330m1 and finish my full translation and open an issue and attach the sdf file till July 15? Yes, we keep updating. The delivery deadlines you should look at are: July 15th - to meet the OOo 3.3 Beta release August 12th - final translation delivery No need to provide anything besides those dates. Thanks, Rafaella The latter was the case until now. Thanks, m. 2010/6/21 Rafaella Braconi rafaella.brac...@sun.com Dear Translators/Localizers, I've created a wiki page gathering information on how to proceed with the translation work for 3.3. http://wiki.services.openoffice.org/wiki/Translation_for_3.3 Milestone 83 can be used to start translation. However, please disregard 2 modules that erroneously have been integrated: testautomation and migrationanalysis. Please note that there is a Beta release scheduled for 3.3. The focus of the Beta release is primarily UI, that means, that it's not a requirement to provide translated Help files. Delivery deadline for the Beta is July 15th. Kind Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. On a side note, I really think we need a version control on the po files... Olivier Em 22-06-2010 04:54, Rafaella Braconi escreveu: Hi Olivier, On 21.06.10 21:48, Olivier Hallot wrote: Hi Rafaella Is Pootle already loaded with the new strings? yes, it has been updated with milestone 83. Because I had a glimpse at the pt-BR strings and had a bad feeling that several files were reset to zero translation, Are you talking about Help or UI strings? Can you provide some examples so that we can try to verify? Thanks, rafaella or there is a shuffling among them and no track on what have changed. Also, looking at the feature freeze page, it seems to me that we should not have that much to translate. Thanks Regards Em 21-06-2010 13:42, Rafaella Braconi escreveu: Hi André, André Schnabel ha scritto: Hi, Am 21.06.2010 18:13, schrieb Rafaella Braconi: Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches hmm but this would mean, that second handover will bring almost no more new strings in? Can you confirm this? With the m83 almost all changes - especially in the Help - have already been integrated. With the second handoff there will be some additional changes, but at the moment I don't have any estimates about their volume. As soon as I have any updates, I'll let you know. In the meanwhile, I would encourage all the teams to use this time to translate before the second handoff. Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Olivier, Modules were migrated from svx to cui (i.e. source code were moved from one module to another). In an ideal world all translations would have been copied, too and not offered again for translation. We need to find an easy way to automatically leverage old translations. Regards, Andras 2010/6/22 Olivier Hallot ohal...@openoffice.org: Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. Same for German here. *but* this is normal behavior having our current workflow in mind. some developer decided to shuffle source strings from location A to location B - our workflow does not apply atuomatic translation to such changes (last time this happened, it seemed as if developers are not aware of the l10n workload they are causing). On a side note, I really think we need a version control on the po files... Yes, would also be nice to have, but would not solve the specific problem. I did not check yet, if the strings at the new location can be translated automatic. Regards, André -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Andre Schnabel wrote: Hi, In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. Same for German here. *but* this is normal behavior having our current workflow in mind. some developer decided to shuffle source strings from location A to location B - our workflow does not apply atuomatic translation to such changes (last time this happened, it seemed as if developers are not aware of the l10n workload they are causing). On a side note, I really think we need a version control on the po files... Yes, would also be nice to have, but would not solve the specific problem. I did not check yet, if the strings at the new location can be translated automatic. It can for more than 90% of them, but you have to check for it any way... Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
У уто, 22. 06 2010. у 06:59 -0300, Olivier Hallot пише: Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is same as what I got when converting SDF to POT and using pomigrate2 to merge with old translations. Let us look at macropg.src#RID_SVXSTR_EVENT_SAVEDOC.string.text. Before it was in svx/source/dialog.po and now it is in cui/source/customize.po When running [pomigrate2 -C -F ui uinew pot] some of these messages where not kept as translated, while some are. I have 158 translated and 27 not translated in cui/source/customize.po after the merge. I am thinking about writing a replacement for pomigrate2 that will keep track of reference ids when merging. Currently as a workaround I am using msgmerge to manually re-merge old translations when situation like this happens. Goran - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Von: Sophie sgautier@free.fr It can for more than 90% of them, but you have to check for it any way... Yes, but verification of a string is less then one second in most cases vs. up to several minutes for a new translation ;) Regards, André -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Olivier, On 22.06.10 11:59, Olivier Hallot wrote: Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx32/ In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... Rafaella Olivier Em 22-06-2010 04:54, Rafaella Braconi escreveu: Hi Olivier, On 21.06.10 21:48, Olivier Hallot wrote: Hi Rafaella Is Pootle already loaded with the new strings? yes, it has been updated with milestone 83. Because I had a glimpse at the pt-BR strings and had a bad feeling that several files were reset to zero translation, Are you talking about Help or UI strings? Can you provide some examples so that we can try to verify? Thanks, rafaella or there is a shuffling among them and no track on what have changed. Also, looking at the feature freeze page, it seems to me that we should not have that much to translate. Thanks Regards Em 21-06-2010 13:42, Rafaella Braconi escreveu: Hi André, André Schnabel ha scritto: Hi, Am 21.06.2010 18:13, schrieb Rafaella Braconi: Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches hmm but this would mean, that second handover will bring almost no more new strings in? Can you confirm this? With the m83 almost all changes - especially in the Help - have already been integrated. With the second handoff there will be some additional changes, but at the moment I don't have any estimates about their volume. As soon as I have any updates, I'll let you know. In the meanwhile, I would encourage all the teams to use this time to translate before the second handoff. Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Von: Rafaella Braconi rafaella.brac...@sun.com On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... Pootle (or more precise translate toolkit) can use old translation files (set of po files) as translation memory. I'd guess, using pretranslate instead of pomerge would give much more fuzzy matches (so that you only need to check instead of translate). Still did not test this - quite busiy with other things atm :( Regards, André -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
In data martedì 22 giugno 2010 14:42:35, Rafaella Braconi ha scritto: : Hi Olivier, On 22.06.10 11:59, Olivier Hallot wrote: Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localizati on/tmx32/ In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... Hi, Hey, where's Italian tmx files? Am I wrong or something is missing? BTW, these tmx are old and not updated with some very recent corrections... -- Valter Registered Linux User #466410 http://counter.li.org Kubuntu Linux: www.kubuntu.org OpenOffice: www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
In data martedì 22 giugno 2010 14:42:35, Rafaella Braconi ha scritto: : Hi Olivier, On 22.06.10 11:59, Olivier Hallot wrote: Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localizati on/tmx32/ Maybe Italian strings are in the eu files? Regards, -- Valter Registered Linux User #466410 http://counter.li.org Kubuntu Linux: www.kubuntu.org OpenOffice: www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
In data martedì 22 giugno 2010 14:42:35, Rafaella Braconi ha scritto: Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localizati on/tmx32/ I do confirm, with regret, I cannot found an updated tmx for Italian... Ciao -- Valter Registered Linux User #466410 http://counter.li.org Kubuntu Linux: www.kubuntu.org OpenOffice: www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
On Mon, Jun 21, 2010 at 11:29 PM, Khoem Sokhem khoemsok...@khmeros.info wrote: Hello, I saw the file in .../devel/DEV300/DEV300_m83/Build-1/POT/ only 1KB of size. I think it is not a valid POT file for translating. Could the file be located other location beside the a bove location? Thanks, Sokhem I didn't see this answered and I have the same problem - are there POT files available somewhere for m83? Thanks Kevin - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Am 22.06.2010 21:39, schrieb Goran Rakic: У уто, 22. 06 2010. у 16:10 -0300, Olivier Hallot пише: Hi Rafaella dev's I would like to express my deep disapointment with this situation. I will second that, but for what I know the problem here is in our PO toolkit, not in the process how developers work. Things can easily improve by creating a new tool for merging POTs created from SDF file with old PO files that could cope up with code moving from one module into another. If there are no voices against it I can work on this during July so we can test and improve it later and make it ready for next release cycle. Hmm .. I'm not really keen of having yet another tool. If we are working on something, this should be done within translate toolkit. The pretranslate tool from translate toolkit is supposed to do exactly what we need - unfortunately it doesn't work the way we need it. At least not for xliff - did anybody try with .po? I also did not check, how successfull pretranslate works with translation memories. Unfortunately pretranslate manpage gives no information, what format to use as translation memory file. In fact - for my own workflow (using xliff files, OLTE and built in translation memory which is based on the translations I did so far) gives ~ 60% automatic transaltions for the moved strings. My translatoin memory does not contain all the previus translations, therefore the rather low rate. Unfortunately there is no german tmx file at ooo.services :( So for me - before starting a new tool I'd recommend: - to provide .tmx files based on previous translations for all languages - try to improve translate toolkit - teach developers about the workload some acitivities cause here, that seem to be very simple for developers and find some way to move l10n strings along with the original english strings regards, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Dear Translators/Localizers, I've created a wiki page gathering information on how to proceed with the translation work for 3.3. http://wiki.services.openoffice.org/wiki/Translation_for_3.3 Milestone 83 can be used to start translation. However, please disregard 2 modules that erroneously have been integrated: testautomation and migrationanalysis. Please note that there is a Beta release scheduled for 3.3. The focus of the Beta release is primarily UI, that means, that it's not a requirement to provide translated Help files. Delivery deadline for the Beta is July 15th. Kind Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Rafaella, Am 21.06.2010 17:43, schrieb Rafaella Braconi: I've created a wiki page gathering information on how to proceed with the translation work for 3.3. http://wiki.services.openoffice.org/wiki/Translation_for_3.3 Thanks for the update, but I wonder if the estimated wordcount is correct. Wiki tells: DEV300 m83 (for the ones who have translated 3.2.1) UI: approx. 8000 words Help: approx. 11000 words but the curect update already introduced UI: ~9000 words Help: ~2 words It's very hard to plan our translation schedule and estimate any date for delivery based on this information :( Regards, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches It's very hard to plan our translation schedule and estimate any date for delivery based on this information :( I am glad to provide you any additional information. Just let me know, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Am 21.06.2010 18:13, schrieb Rafaella Braconi: Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches hmm but this would mean, that second handover will bring almost no more new strings in? Can you confirm this? Regards, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi André, André Schnabel ha scritto: Hi, Am 21.06.2010 18:13, schrieb Rafaella Braconi: Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches hmm but this would mean, that second handover will bring almost no more new strings in? Can you confirm this? With the m83 almost all changes - especially in the Help - have already been integrated. With the second handoff there will be some additional changes, but at the moment I don't have any estimates about their volume. As soon as I have any updates, I'll let you know. In the meanwhile, I would encourage all the teams to use this time to translate before the second handoff. Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi Rafaella Is Pootle already loaded with the new strings? Because I had a glimpse at the pt-BR strings and had a bad feeling that several files were reset to zero translation, or there is a shuffling among them and no track on what have changed. Also, looking at the feature freeze page, it seems to me that we should not have that much to translate. Thanks Regards Em 21-06-2010 13:42, Rafaella Braconi escreveu: Hi André, André Schnabel ha scritto: Hi, Am 21.06.2010 18:13, schrieb Rafaella Braconi: Hi André, but the curect update already introduced UI: ~9000 words Help: ~2 words You are completely right. I forgot to add the fuzzy matches hmm but this would mean, that second handover will bring almost no more new strings in? Can you confirm this? With the m83 almost all changes - especially in the Help - have already been integrated. With the second handoff there will be some additional changes, but at the moment I don't have any estimates about their volume. As soon as I have any updates, I'll let you know. In the meanwhile, I would encourage all the teams to use this time to translate before the second handoff. Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org -- Olivier Hallot OpenOffice.org L10n Leader for Brazilian Portuguese Rio de Janeiro - Brasil - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Rafaella, I am singlehandedly working on the Slovenian translation and have my own localization server. I have regularly updated my files so yesterday I had just one fuzzy string left with the updated m83. If I understand you correctly, even if I am not working via Pootle, I have to send the sdf to you (or add it to an issue) before July 1, so that you get a almost-fully-translated stuff for all languages into the tree and then update my files after July 1? Or do I keep updating to new m84, m85 etc. until OOO330m1 and finish my full translation and open an issue and attach the sdf file till July 15? The latter was the case until now. Thanks, m. 2010/6/21 Rafaella Braconi rafaella.brac...@sun.com Dear Translators/Localizers, I've created a wiki page gathering information on how to proceed with the translation work for 3.3. http://wiki.services.openoffice.org/wiki/Translation_for_3.3 Milestone 83 can be used to start translation. However, please disregard 2 modules that erroneously have been integrated: testautomation and migrationanalysis. Please note that there is a Beta release scheduled for 3.3. The focus of the Beta release is primarily UI, that means, that it's not a requirement to provide translated Help files. Delivery deadline for the Beta is July 15th. Kind Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hello, I saw the file in .../devel/DEV300/DEV300_m83/Build-1/POT/ only 1KB of size. I think it is not a valid POT file for translating. Could the file be located other location beside the a bove location? Thanks, Sokhem Dear Translators/Localizers, I've created a wiki page gathering information on how to proceed with the translation work for 3.3. http://wiki.services.openoffice.org/wiki/Translation_for_3.3 Milestone 83 can be used to start translation. However, please disregard 2 modules that erroneously have been integrated: testautomation and migrationanalysis. Please note that there is a Beta release scheduled for 3.3. The focus of the Beta release is primarily UI, that means, that it's not a requirement to provide translated Help files. Delivery deadline for the Beta is July 15th. Kind Regards, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
