Re: [l10n-dev] No source to translate ?
Hi André After many trials and errors, I was able to pretranslate cui.po with the following command: pretranslate -i cui.po -t _old_version_of_dialog.po -o translated_cui.po Thanks Olivier Olivier Hallot escreveu: Thank you André for the tip. Unfortunately, although I have UI 3.1 archived in my notebook, the results of the pretranslate (version 1.3, though) command are no good at all. I get a full migration of the old (3.1) dialog.po in translated_cui.po but cui.po has 1821 strings and (3.1) dialog.po has 2719 strings. A mismatch. Then I tried to copy the commented strings from the (new) dialog.po (suposedly the same as cui.po) but it is not so funny to rebuild a valid po file by simple cut paste plus edition, and I get a broken po file (msgctxt polluting msgtxt strings and no more #-comments). So I kindly ask the l10n team to supply cui.po with the already translated strings available in dialog.po, I really would like to avoid 1821 strings rework (*). Thanks Olivier (*) Yes, I use KBabel with TM, but it is nevertheless *not* error prone and very time consuming. André Schnabel escreveu: Hi, Olivier Hallot schrieb: The strings have been moved to cui.po ! Saddly, the strings were moved but the translation not... It could spare us many hours of work and mistakes hunt... Any chances to get our translated strings loaded in cui.po? If you have the previous version of dialog.po (containing your old translations) yes - this would be possible. In this case you need the translate toolkit (http://sourceforge.net/projects/translate/files/Translate%20Toolkit/1.4.0/) and then run pretranslate -t cui.po -i _old_version_of_dialog.po -o translated_cui.po Maybe this is also possible with the current version of dialog.po, if you remove the comment marks. (I did not check, as I don't work with po files). Some basic recommendations: - download the full zip-archive of your translation before major translation updates in pootle (so that you have your own archives) - use some Computer Aided Translation tools with good translation memory support (this will save a lot of time esp. for UI-translation) - install translation toolkit and spend some time to work with it (This will give you an idea how pootle threads the files internally) I registered da BOF session for Oriveto on Best practices translating OOo (with kind support from Rafaella). I hope, we can discuss and collect more recommendations there. André - 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 Scinergy Consulting Tel (021) 2224-3224, (021) 8822-8812 Rio de Janeiro, Brasil http://www.scinergy.com.br OpenOffice.org L10N project leader for Brazil - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Thank you André for the tip. Unfortunately, although I have UI 3.1 archived in my notebook, the results of the pretranslate (version 1.3, though) command are no good at all. I get a full migration of the old (3.1) dialog.po in translated_cui.po but cui.po has 1821 strings and (3.1) dialog.po has 2719 strings. A mismatch. Then I tried to copy the commented strings from the (new) dialog.po (suposedly the same as cui.po) but it is not so funny to rebuild a valid po file by simple cut paste plus edition, and I get a broken po file (msgctxt polluting msgtxt strings and no more #-comments). So I kindly ask the l10n team to supply cui.po with the already translated strings available in dialog.po, I really would like to avoid 1821 strings rework (*). Thanks Olivier (*) Yes, I use KBabel with TM, but it is nevertheless *not* error prone and very time consuming. André Schnabel escreveu: Hi, Olivier Hallot schrieb: The strings have been moved to cui.po ! Saddly, the strings were moved but the translation not... It could spare us many hours of work and mistakes hunt... Any chances to get our translated strings loaded in cui.po? If you have the previous version of dialog.po (containing your old translations) yes - this would be possible. In this case you need the translate toolkit (http://sourceforge.net/projects/translate/files/Translate%20Toolkit/1.4.0/) and then run pretranslate -t cui.po -i _old_version_of_dialog.po -o translated_cui.po Maybe this is also possible with the current version of dialog.po, if you remove the comment marks. (I did not check, as I don't work with po files). Some basic recommendations: - download the full zip-archive of your translation before major translation updates in pootle (so that you have your own archives) - use some Computer Aided Translation tools with good translation memory support (this will save a lot of time esp. for UI-translation) - install translation toolkit and spend some time to work with it (This will give you an idea how pootle threads the files internally) I registered da BOF session for Oriveto on Best practices translating OOo (with kind support from Rafaella). I hope, we can discuss and collect more recommendations there. André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org -- Olivier Hallot OpenOffice.org L10N project leader for Brazil - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
These messages are generated by gettext's msgmerge and there is a key for switching this. I think that these obsolete messages are usually not needed. `--previous' Keep the previous msgids of translated messages, marked with `#|', when adding the fuzzy marker to such messages. Ain On Mon, Aug 24, 2009 at 08:55, Dwayne Baileydwa...@translate.org.za wrote: Hi All, On Mon, 2009-08-24 at 10:42 +0800, Aijin Kim wrote: Hi Dick and all, Sophie wrote: Dick Groskamp wrote: Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. Yes, you're right so this bug has to be reported to the Pootle team. I forwarded this issue to Friedel who is the Pootle developer. Let's wait for his reply if it's a known bug. Friedel and a number of other Pootle coders have been in Egypt at Pootlemania for a code sprint. He is back so I'm sure he'll chip in today if needed. I've had a quick look at the issue and I'll try summarise then explain the issue so that everyone gets an idea of what's going on even if you don't care for code! Here is the bug that I've raised to track this: http://bugs.locamotion.org/show_bug.cgi?id=1114 Issue = These strings are being presented by Pootle because Pootle is seeing obsolete messages (marked as #~ in PO files) as untranslated. There is nothing wrong with the PO files which is why translators who are using offline tools are not seeing the issue. Fix === Fortunately I don't think the fix will be too hard and it will probably be easy to patch the OOo Pootle server. I'm hopeful that we'll be able to have a fix before the end of today. So you might not need to try any of the following workarounds. Workaround == 1) Ignore these messages with no source text until we fix the issue. 2) Try work offline by downloading and uploading PO files to Pootle. (There have been a few suggestions of possible tools, you can also try out Virtaal http://virtaal.org/) Issue in more detail Pootle uses the Translate Toolkit to do much of its manipulation of PO files. We did a major work in the Translate Toolkit for v1.4 where we removed the old KDE style comments and replaced them with proper Gettext msgctxt. The change was important as it meant that we got proper PO files for OpenOffice.org and did away with the non-standard KDE comments. Many PO editors didn't understand KDE comments and it could lead to translators being confused and translating the KDE comment instead of ignoring them. It was an invasive change, we knew that, but the benefits were great. We tested quite extensively doing roundtrip test but unfortunately it seemed the change has impacted our code that tracks the state of a string. I.e. whether a string is translated, fuzzy, untranslated or obsolete. The toolkit is now seeing an obsolete message with msgctxt as untranslated when it should be ignoring them completely. Pootle relies on this state information to find untranslated strings and is thus finding them and presenting them to you even though they should be ignored. The bad news is that our battery of unit tests didn't check for this condition so it slipped through in our changes. The fix should be as simple as to ensure that obsolete messages with a msgctxt field are not seen as untranslated. Please feel free to join the bug but I'm sure we'll announce the fix on the list. -- Dwayne Bailey Associate Research Director +27 12 460 1095 (w) Translate.org.za ANLoc +27 83 443 7114 (c) Recent blog posts: * Google Translate + libtranslate + Virtaal = machine translation in 7 new languages http://www.translate.org.za/blogs/dwayne/en/content/google-translate-libtranslate-virtaal-machine-translation-7-new-languages * Fixes for Skype Video, Webcam on Fedora * libtranslate, TM plugins and Virtaal Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ - 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:
Re: [l10n-dev] No source to translate ?
Fixed. The bug is fixed and I've sent info to Aijin to allow the OOo Pootle server to be updated. So I don't think you will need to apply any of the workaround suggestions. On Mon, 2009-08-24 at 07:55 +0200, Dwayne Bailey wrote: Hi All, On Mon, 2009-08-24 at 10:42 +0800, Aijin Kim wrote: Hi Dick and all, Sophie wrote: Dick Groskamp wrote: Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. Yes, you're right so this bug has to be reported to the Pootle team. I forwarded this issue to Friedel who is the Pootle developer. Let's wait for his reply if it's a known bug. Friedel and a number of other Pootle coders have been in Egypt at Pootlemania for a code sprint. He is back so I'm sure he'll chip in today if needed. I've had a quick look at the issue and I'll try summarise then explain the issue so that everyone gets an idea of what's going on even if you don't care for code! Here is the bug that I've raised to track this: http://bugs.locamotion.org/show_bug.cgi?id=1114 Issue = These strings are being presented by Pootle because Pootle is seeing obsolete messages (marked as #~ in PO files) as untranslated. There is nothing wrong with the PO files which is why translators who are using offline tools are not seeing the issue. Fix === Fortunately I don't think the fix will be too hard and it will probably be easy to patch the OOo Pootle server. I'm hopeful that we'll be able to have a fix before the end of today. So you might not need to try any of the following workarounds. Workaround == 1) Ignore these messages with no source text until we fix the issue. 2) Try work offline by downloading and uploading PO files to Pootle. (There have been a few suggestions of possible tools, you can also try out Virtaal http://virtaal.org/) Issue in more detail Pootle uses the Translate Toolkit to do much of its manipulation of PO files. We did a major work in the Translate Toolkit for v1.4 where we removed the old KDE style comments and replaced them with proper Gettext msgctxt. The change was important as it meant that we got proper PO files for OpenOffice.org and did away with the non-standard KDE comments. Many PO editors didn't understand KDE comments and it could lead to translators being confused and translating the KDE comment instead of ignoring them. It was an invasive change, we knew that, but the benefits were great. We tested quite extensively doing roundtrip test but unfortunately it seemed the change has impacted our code that tracks the state of a string. I.e. whether a string is translated, fuzzy, untranslated or obsolete. The toolkit is now seeing an obsolete message with msgctxt as untranslated when it should be ignoring them completely. Pootle relies on this state information to find untranslated strings and is thus finding them and presenting them to you even though they should be ignored. The bad news is that our battery of unit tests didn't check for this condition so it slipped through in our changes. The fix should be as simple as to ensure that obsolete messages with a msgctxt field are not seen as untranslated. Please feel free to join the bug but I'm sure we'll announce the fix on the list. -- Dwayne Bailey Associate Research Director+27 12 460 1095 (w) Translate.org.za ANLoc+27 83 443 7114 (c) Recent blog posts: * Google Translate + libtranslate + Virtaal = machine translation in 7 new languages http://www.translate.org.za/blogs/dwayne/en/content/google-translate-libtranslate-virtaal-machine-translation-7-new-languages * Fixes for Skype Video, Webcam on Fedora * libtranslate, TM plugins and Virtaal Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org -- Dwayne Bailey Associate Research Director+27 12 460 1095 (w) Translate.org.za ANLoc+27 83 443 7114 (c) Recent blog posts: * Google Translate + libtranslate + Virtaal = machine translation in 7 new languages
Re: [l10n-dev] No source to translate ?
Hi André Schnabel escreveu: Hi, Dick Groskamp schrieb: Dick Groskamp schreef: And several in: OO.o PO UI / svx / source / dialog.po namely: align.src#RID_SVXPAGE_ALIGNMENT.FT_HORALIGN.fixedtext.text how do you actually do the translation? these strings are just comments in http://pootle.sunvirtuallab.com/nl/openoffice_org/svx/source/dialog.po so you never should get these strings while translating this file. The strings have been moved to cui.po ! Saddly, the strings were moved but the translation not... It could spare us many hours of work and mistakes hunt... Any chances to get our translated strings loaded in cui.po? -- Olivier Hallot OpenOffice.org L10N project leader for Brazil - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Hi, Olivier Hallot schrieb: The strings have been moved to cui.po ! Saddly, the strings were moved but the translation not... It could spare us many hours of work and mistakes hunt... Any chances to get our translated strings loaded in cui.po? If you have the previous version of dialog.po (containing your old translations) yes - this would be possible. In this case you need the translate toolkit (http://sourceforge.net/projects/translate/files/Translate%20Toolkit/1.4.0/) and then run pretranslate -t cui.po -i _old_version_of_dialog.po -o translated_cui.po Maybe this is also possible with the current version of dialog.po, if you remove the comment marks. (I did not check, as I don't work with po files). Some basic recommendations: - download the full zip-archive of your translation before major translation updates in pootle (so that you have your own archives) - use some Computer Aided Translation tools with good translation memory support (this will save a lot of time esp. for UI-translation) - install translation toolkit and spend some time to work with it (This will give you an idea how pootle threads the files internally) I registered da BOF session for Oriveto on Best practices translating OOo (with kind support from Rafaella). I hope, we can discuss and collect more recommendations there. André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Hi all, The patch has been applied to the OO.o Pootle. Regards, Aijin Dwayne Bailey wrote: Fixed. The bug is fixed and I've sent info to Aijin to allow the OOo Pootle server to be updated. So I don't think you will need to apply any of the workaround suggestions. On Mon, 2009-08-24 at 07:55 +0200, Dwayne Bailey wrote: Hi All, On Mon, 2009-08-24 at 10:42 +0800, Aijin Kim wrote: Hi Dick and all, Sophie wrote: Dick Groskamp wrote: Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. Yes, you're right so this bug has to be reported to the Pootle team. I forwarded this issue to Friedel who is the Pootle developer. Let's wait for his reply if it's a known bug. Friedel and a number of other Pootle coders have been in Egypt at Pootlemania for a code sprint. He is back so I'm sure he'll chip in today if needed. I've had a quick look at the issue and I'll try summarise then explain the issue so that everyone gets an idea of what's going on even if you don't care for code! Here is the bug that I've raised to track this: http://bugs.locamotion.org/show_bug.cgi?id=1114 Issue = These strings are being presented by Pootle because Pootle is seeing obsolete messages (marked as #~ in PO files) as untranslated. There is nothing wrong with the PO files which is why translators who are using offline tools are not seeing the issue. Fix === Fortunately I don't think the fix will be too hard and it will probably be easy to patch the OOo Pootle server. I'm hopeful that we'll be able to have a fix before the end of today. So you might not need to try any of the following workarounds. Workaround == 1) Ignore these messages with no source text until we fix the issue. 2) Try work offline by downloading and uploading PO files to Pootle. (There have been a few suggestions of possible tools, you can also try out Virtaal http://virtaal.org/) Issue in more detail Pootle uses the Translate Toolkit to do much of its manipulation of PO files. We did a major work in the Translate Toolkit for v1.4 where we removed the old KDE style comments and replaced them with proper Gettext msgctxt. The change was important as it meant that we got proper PO files for OpenOffice.org and did away with the non-standard KDE comments. Many PO editors didn't understand KDE comments and it could lead to translators being confused and translating the KDE comment instead of ignoring them. It was an invasive change, we knew that, but the benefits were great. We tested quite extensively doing roundtrip test but unfortunately it seemed the change has impacted our code that tracks the state of a string. I.e. whether a string is translated, fuzzy, untranslated or obsolete. The toolkit is now seeing an obsolete message with msgctxt as untranslated when it should be ignoring them completely. Pootle relies on this state information to find untranslated strings and is thus finding them and presenting them to you even though they should be ignored. The bad news is that our battery of unit tests didn't check for this condition so it slipped through in our changes. The fix should be as simple as to ensure that obsolete messages with a msgctxt field are not seen as untranslated. Please feel free to join the bug but I'm sure we'll announce the fix on the list. -- Dwayne Bailey Associate Research Director+27 12 460 1095 (w) Translate.org.za ANLoc+27 83 443 7114 (c) Recent blog posts: * Google Translate + libtranslate + Virtaal = machine translation in 7 new languages http://www.translate.org.za/blogs/dwayne/en/content/google-translate-libtranslate-virtaal-machine-translation-7-new-languages * Fixes for Skype Video, Webcam on Fedora * libtranslate, TM plugins and Virtaal Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ - 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] No source to translate ?
André Schnabel schreef: how do you actually do the translation? All in Pootle (on line) these strings are just comments in http://pootle.sunvirtuallab.com/nl/openoffice_org/svx/source/dialog.po so you never should get these strings while translating this file. The strings have been moved to cui.po ! Ah - I just tried in pootle - it's definately a bug there. Pootle filter picks those strings up and provides them for translation - definately a pootle bug. Yep, that is where I found them too. Silly me was thinking that POOTLE should ONLY contain up to date files building up with new strings etc. etc every time a new release comes out. I'm am no technician, just a simple translator. I will translate anything you put in POOTLE. I hope other people can prevent POOTLE from gaining this type of mishaps. All these strings are indiacted as UNTRANSLATED. They never should have !! Please let us know how to handle these and please let us know if this is correct or that something somewhere went wrong ? I'd strongly recommend to *not* use pootle for larger translation work. Download the files, translate offline with some more advanced translation editor andthe upload to pootle again. Well, that is also a possibility but that will not keep this unwanted strings out, I presume.. My point is that these strings will never have to be called UNTRANSLATED, because they are (reading Sophie's and your post) obviously deprecated. If they are removed from the program, why keep them ? In POOTLE I will have to go over eacht and every entry and have to hit the SUBMIT button. Is there there someone out there who can shine some light on this? I'have no idea where thes strings came from so . -- DiGro Windows XP Professional SP2 and OOo 3.0 Scanned with: Ziggo uitgebreide internetbeveiliging - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Hi Dick, Dick Groskamp wrote: André Schnabel schreef: how do you actually do the translation? All in Pootle (on line) these strings are just comments in http://pootle.sunvirtuallab.com/nl/openoffice_org/svx/source/dialog.po so you never should get these strings while translating this file. The strings have been moved to cui.po ! Ah - I just tried in pootle - it's definately a bug there. Pootle filter picks those strings up and provides them for translation - definately a pootle bug. Yep, that is where I found them too. Silly me was thinking that POOTLE should ONLY contain up to date files building up with new strings etc. etc every time a new release comes out. I'm am no technician, just a simple translator. I will translate anything you put in POOTLE. I hope other people can prevent POOTLE from gaining this type of mishaps. All these strings are indiacted as UNTRANSLATED. They never should have !! Please let us know how to handle these and please let us know if this is correct or that something somewhere went wrong ? I'd strongly recommend to *not* use pootle for larger translation work. Download the files, translate offline with some more advanced translation editor andthe upload to pootle again. Well, that is also a possibility but that will not keep this unwanted strings out, I presume.. My point is that these strings will never have to be called UNTRANSLATED, because they are (reading Sophie's and your post) obviously deprecated. If they are removed from the program, why keep them ? In POOTLE I will have to go over eacht and every entry and have to hit the SUBMIT button. Is there there someone out there who can shine some light on this? I'have no idea where thes strings came from so . As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. 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] No source to translate ?
Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. I shall probably proceed off line and will (as you and Andre indicate) loose those strings. And yes, I will also have to make my terminology project appear in Pootle. Been pushing that forward for some time now Thanks again -- DiGro Windows XP Professional SP2 and OOo 3.0 Scanned with: Ziggo uitgebreide internetbeveiliging - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
On Aug 24, 2009, at 4:52 AM, Sophie wrote: And yes, I will also have to make my terminology project appear in Pootle. Been pushing that forward for some time now I don't know what is your operating system, but there is several tools that allow you to translate like OmegaT, OTE, and I use PoEdit and its TM. I/we find it more convenient than Pootle, even if there is still some ehnancement to bring to these tools. OmegaT, OTE and PoEdit are available on OSX/Windows/Linux (I've suggested a few lines to Andre for the OTE manual so that OSX users easily figure out how to make it start). Jean-Christophe Helary - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Hi Dick and all, Sophie wrote: Dick Groskamp wrote: Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. Yes, you're right so this bug has to be reported to the Pootle team. I forwarded this issue to Friedel who is the Pootle developer. Let's wait for his reply if it's a known bug. Thanks, Aijin I shall probably proceed off line and will (as you and Andre indicate) loose those strings. not loose them, but be able to ignore them safely :) And yes, I will also have to make my terminology project appear in Pootle. Been pushing that forward for some time now I don't know what is your operating system, but there is several tools that allow you to translate like OmegaT, OTE, and I use PoEdit and its TM. I/we find it more convenient than Pootle, even if there is still some ehnancement to bring to these tools. Thanks again you're welcome, we are a team to help each other :) Kind regards Sophie - 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] No source to translate ?
Hi All, On Mon, 2009-08-24 at 10:42 +0800, Aijin Kim wrote: Hi Dick and all, Sophie wrote: Dick Groskamp wrote: Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. Yes, you're right so this bug has to be reported to the Pootle team. I forwarded this issue to Friedel who is the Pootle developer. Let's wait for his reply if it's a known bug. Friedel and a number of other Pootle coders have been in Egypt at Pootlemania for a code sprint. He is back so I'm sure he'll chip in today if needed. I've had a quick look at the issue and I'll try summarise then explain the issue so that everyone gets an idea of what's going on even if you don't care for code! Here is the bug that I've raised to track this: http://bugs.locamotion.org/show_bug.cgi?id=1114 Issue = These strings are being presented by Pootle because Pootle is seeing obsolete messages (marked as #~ in PO files) as untranslated. There is nothing wrong with the PO files which is why translators who are using offline tools are not seeing the issue. Fix === Fortunately I don't think the fix will be too hard and it will probably be easy to patch the OOo Pootle server. I'm hopeful that we'll be able to have a fix before the end of today. So you might not need to try any of the following workarounds. Workaround == 1) Ignore these messages with no source text until we fix the issue. 2) Try work offline by downloading and uploading PO files to Pootle. (There have been a few suggestions of possible tools, you can also try out Virtaal http://virtaal.org/) Issue in more detail Pootle uses the Translate Toolkit to do much of its manipulation of PO files. We did a major work in the Translate Toolkit for v1.4 where we removed the old KDE style comments and replaced them with proper Gettext msgctxt. The change was important as it meant that we got proper PO files for OpenOffice.org and did away with the non-standard KDE comments. Many PO editors didn't understand KDE comments and it could lead to translators being confused and translating the KDE comment instead of ignoring them. It was an invasive change, we knew that, but the benefits were great. We tested quite extensively doing roundtrip test but unfortunately it seemed the change has impacted our code that tracks the state of a string. I.e. whether a string is translated, fuzzy, untranslated or obsolete. The toolkit is now seeing an obsolete message with msgctxt as untranslated when it should be ignoring them completely. Pootle relies on this state information to find untranslated strings and is thus finding them and presenting them to you even though they should be ignored. The bad news is that our battery of unit tests didn't check for this condition so it slipped through in our changes. The fix should be as simple as to ensure that obsolete messages with a msgctxt field are not seen as untranslated. Please feel free to join the bug but I'm sure we'll announce the fix on the list. -- Dwayne Bailey Associate Research Director+27 12 460 1095 (w) Translate.org.za ANLoc+27 83 443 7114 (c) Recent blog posts: * Google Translate + libtranslate + Virtaal = machine translation in 7 new languages http://www.translate.org.za/blogs/dwayne/en/content/google-translate-libtranslate-virtaal-machine-translation-7-new-languages * Fixes for Skype Video, Webcam on Fedora * libtranslate, TM plugins and Virtaal Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Dick Groskamp schreef: Came across this one: [cut] There is no source text. I thought I saw some more of these but at first let them be. Now I'm wondering what to do with these. Sorry about the mess above. Here is another one: convert.src#DLG_CONV_TEXT_TABLE.FT_REPEAT_HEADER.fixedtext.text in OO.o PO UI / sw / source / ui / table.po Again: no source text -- DiGro Windows XP Professional SP2 and OOo 3.0 Scanned with: Ziggo uitgebreide internetbeveiliging - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Dick Groskamp schreef: And several in: OO.o PO UI / svx / source / dialog.po namely: align.src#RID_SVXPAGE_ALIGNMENT.FT_HORALIGN.fixedtext.text align.src#RID_SVXPAGE_ALIGNMENT.LB_HORALIGN.5.stringlist.text align.src#RID_SVXPAGE_ALIGNMENT.FT_VERALIGN.fixedtext.text align.src#RID_SVXPAGE_ALIGNMENT.LB_VERALIGN.3.stringlist.text align.src#RID_SVXPAGE_ALIGNMENT.FL_WRAP.fixedline.text autocdlg.src#RID_OFA_AUTOCORR_DLG.1.RID_OFAPAGE_AUTOCORR_QUOTE.pageitem.text autocdlg.src#RID_OFA_AUTOCORR_DLG.1.RID_OFAPAGE_AUTOCOMPLETE_OPTIONS.pageitem.text autocdlg.src#RID_OFA_AUTOCORR_DLG.1.RID_OFAPAGE_SMARTTAG_OPTIONS.pageitem.text autocdlg.src#RID_OFAPAGE_AUTOCORR_OPTIONS.tabpage.text autocdlg.src#RID_OFAPAGE_AUTOFMT_APPLY.PB_EDIT.pushbutton.text autocdlg.src#RID_OFAPAGE_AUTOCORR_REPLACE.FT_SHORT.fixedtext.text autocdlg.src#RID_OFAPAGE_AUTOCORR_REPLACE.PB_NEW_REPLACE.pushbutton.text autocdlg.src#RID_OFAPAGE_AUTOCORR_EXCEPT.PB_NEWABBREV.pushbutton.text autocdlg.src#RID_OFAPAGE_AUTOCORR_QUOTE.CB_SGL_TYPO.checkbox.text then I stopped. Please let us know how to handle these and please let us know if this is correct or that something somewhere went wrong ? Greetings -- DiGro Windows XP Professional SP2 and OOo 3.0 Scanned with: Ziggo uitgebreide internetbeveiliging - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
Hi Dick Dick Groskamp wrote: Dick Groskamp schreef: And several in: OO.o PO UI / svx / source / dialog.po namely: align.src#RID_SVXPAGE_ALIGNMENT.FT_HORALIGN.fixedtext.text outdated align.src#RID_SVXPAGE_ALIGNMENT.LB_HORALIGN.5.stringlist.text outdated align.src#RID_SVXPAGE_ALIGNMENT.FT_VERALIGN.fixedtext.text outdated align.src#RID_SVXPAGE_ALIGNMENT.LB_VERALIGN.3.stringlist.text I don't find this one align.src#RID_SVXPAGE_ALIGNMENT.FL_WRAP.fixedline.text outdated autocdlg.src#RID_OFA_AUTOCORR_DLG.1.RID_OFAPAGE_AUTOCORR_QUOTE.pageitem.text outdated autocdlg.src#RID_OFA_AUTOCORR_DLG.1.RID_OFAPAGE_AUTOCOMPLETE_OPTIONS.pageitem.text I don't find this one autocdlg.src#RID_OFA_AUTOCORR_DLG.1.RID_OFAPAGE_SMARTTAG_OPTIONS.pageitem.text oudated autocdlg.src#RID_OFAPAGE_AUTOCORR_OPTIONS.tabpage.text outdated autocdlg.src#RID_OFAPAGE_AUTOFMT_APPLY.PB_EDIT.pushbutton.text outdated autocdlg.src#RID_OFAPAGE_AUTOCORR_REPLACE.FT_SHORT.fixedtext.text outdated autocdlg.src#RID_OFAPAGE_AUTOCORR_REPLACE.PB_NEW_REPLACE.pushbutton.text outdated autocdlg.src#RID_OFAPAGE_AUTOCORR_EXCEPT.PB_NEWABBREV.pushbutton.text outdated autocdlg.src#RID_OFAPAGE_AUTOCORR_QUOTE.CB_SGL_TYPO.checkbox.text outdated In sum, this strings are still in the files, but not used any more. I don't know exactly why they are kept, may be if one day we use them again. 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] No source to translate ?
Hi, Dick Groskamp schrieb: Dick Groskamp schreef: And several in: OO.o PO UI / svx / source / dialog.po namely: align.src#RID_SVXPAGE_ALIGNMENT.FT_HORALIGN.fixedtext.text how do you actually do the translation? these strings are just comments in http://pootle.sunvirtuallab.com/nl/openoffice_org/svx/source/dialog.po so you never should get these strings while translating this file. The strings have been moved to cui.po ! Ah - I just tried in pootle - it's definately a bug there. Pootle filter picks those strings up and provides them for translation - definately a pootle bug. Please let us know how to handle these and please let us know if this is correct or that something somewhere went wrong ? I'd strongly recommend to *not* use pootle for larger translation work. Download the files, translate offline with some more advanced translation editor andthe upload to pootle again. André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
