Re: [l10n-dev] m148
So good to see that everyone is positive about this :) Here is a summary of what goes wrong when trying to check the Persian translation using common filters. * acronyms: We translate most of the acronyms into Persian, e.g. CD or URL. The test fails. * brackets: It works well with paranthesis. When it comes to square brackets, it fails since in the right-to-left languages (including Persian) ] stands for opening brackets and comes before [. * doublequoting & singlequoting: The characters used for them in Persian are « and ». So the test fails whenever the message contains quotation marks. * escapes: causes problems when there is \" in the string because of the above problem. * doublewords: The test should check for double words in the original message and should not alert when it contains double words as well. There are messages such as "Dot Dot Dash" among OO.o strings. * endpunc, startpunc, purepunc & puncspacing: Persian doesn't use English punctuation marks. The test fails when we use ؟ for ? and ٪ for %. Comma and Semicolon changes to ، and ؛ in Persian (as well as other right-to-left scripts) so the test fails when the string contains any punctuation marks except the period. Another problem is that the translated string doesn't necessarily keep the word order. For example, there is a string "Automatic *bold* and _underline_". The word-by-word Persian translation would be "*bold* and _underline_ automatic". Both startpunc and endpunc are violated. * numbers: Persian doesn't use European digits for numbers. The test is of no use with Persian digits (Extended Arabic-Indic digits). * sentencecount: it misunderstands floating points with full stops. Persian uses a different character for decimal separator (U+066B). The dot abbreviations also cause problems in counting sentences. * simplecaps & startcaps: Might not be useful even for Latin scripts, since the capitalization pattern could be different from English. Not good for other scripts. Disabling all these filters is almost equal to not using pofilter at all. In fact msgfmt just checks the syntactical correctness of the file. It doesn't do anything more than what pofilter does; but the number of false positive results of poilter is what pushes our translators away. Cheers, fa On دوشنبه, 2006-01-09 at 08:43 +0700, Javier SOLA wrote: > Hi Frazaneh, > > In order to improve the translate toolkit, and make it at least as > usefull for testing as gettext, what do you think should be added to > pofilter? > > Javier > > Farzaneh Sarafraz wrote: > > >What Ain has said neatly fixes everything, but a problem rises for GNU > >gettext users: > >The resulting po files are buggy in their headers. The headers are > >marked fuzzy and the header fields are set to default values. > >This is OK as far as translate-toolkit and sdf files are concerned, but > >it causes GNU gettext tools such as msgfmt report fatal errors. > >Our translators use GNU gettext to test their work since pofilter is > >extremely incompetent in checking the correctness of the translations. > >I would love to hear your views and ideas on this. > >fa > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Farzaneh Sarafraz wrote: What Ain has said neatly fixes everything, but a problem rises for GNU gettext users: The resulting po files are buggy in their headers. The headers are marked fuzzy and the header fields are set to default values. As far as the headers being marked fuzzy, AFAIR the headers are set to fuzzy in .pot files and then marked unfuzzy in .po files when the default values have been filled in. So really if you complete the headers, mark them as unfuzzy, and then do merges from new pot files when updating everything should be OK. If this is incorrect please explain how it should work :-) This is OK as far as translate-toolkit and sdf files are concerned, but it causes GNU gettext tools such as msgfmt report fatal errors. Our translators use GNU gettext to test their work since pofilter is extremely incompetent in checking the correctness of the translations. The tools should be fairly interoperable with gettext once the above is done. pofilter is useful for errors that the South African team has encountered, but takes a bit of getting used to the process of how you check them with it. As Javier said, please feedback more than just saying its incompetent :-) Thanks for the feedback David I would love to hear your views and ideas on this. fa On پنجشنبه, 2006-01-05 at 19:17 +0200, Ain Vagula wrote: Following steps are needed when migrating to UI strings with no duplicates: - install updated toolkit - generate sdf file from your existing translated or half-translated po-s with new toolkit (to avoid english strings in untranslated entries) - backup old po-s somewhere - generate new set of po-files from just generated sdf-file for your language - update generated po-files with latest pot-files. Now every duplicated string in one file has unique identifier, but string itself is translated as it was in your old po-file. Note that: - When you do not regenerate po files, all duplicate entries will be untranslated. - When you use sdf file, generated with old toolkit, for regenerating, untranslated entries will be filled with english strings ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Hi Frazaneh, In order to improve the translate toolkit, and make it at least as usefull for testing as gettext, what do you think should be added to pofilter? Javier Farzaneh Sarafraz wrote: What Ain has said neatly fixes everything, but a problem rises for GNU gettext users: The resulting po files are buggy in their headers. The headers are marked fuzzy and the header fields are set to default values. This is OK as far as translate-toolkit and sdf files are concerned, but it causes GNU gettext tools such as msgfmt report fatal errors. Our translators use GNU gettext to test their work since pofilter is extremely incompetent in checking the correctness of the translations. I would love to hear your views and ideas on this. fa On پنجشنبه, 2006-01-05 at 19:17 +0200, Ain Vagula wrote: Following steps are needed when migrating to UI strings with no duplicates: - install updated toolkit - generate sdf file from your existing translated or half-translated po-s with new toolkit (to avoid english strings in untranslated entries) - backup old po-s somewhere - generate new set of po-files from just generated sdf-file for your language - update generated po-files with latest pot-files. Now every duplicated string in one file has unique identifier, but string itself is translated as it was in your old po-file. Note that: - When you do not regenerate po files, all duplicate entries will be untranslated. - When you use sdf file, generated with old toolkit, for regenerating, untranslated entries will be filled with english strings ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
What Ain has said neatly fixes everything, but a problem rises for GNU gettext users: The resulting po files are buggy in their headers. The headers are marked fuzzy and the header fields are set to default values. This is OK as far as translate-toolkit and sdf files are concerned, but it causes GNU gettext tools such as msgfmt report fatal errors. Our translators use GNU gettext to test their work since pofilter is extremely incompetent in checking the correctness of the translations. I would love to hear your views and ideas on this. fa On پنجشنبه, 2006-01-05 at 19:17 +0200, Ain Vagula wrote: > Following steps are needed when migrating to UI strings with no duplicates: > - install updated toolkit > - generate sdf file from your existing translated or half-translated > po-s with new toolkit (to avoid english strings in untranslated > entries) > - backup old po-s somewhere > - generate new set of po-files from just generated sdf-file for your language > - update generated po-files with latest pot-files. > Now every duplicated string in one file has unique identifier, but > string itself is translated as it was in your old po-file. > Note that: > - When you do not regenerate po files, all duplicate entries will be > untranslated. > - When you use sdf file, generated with old toolkit, for regenerating, > untranslated entries will be filled with english strings > > ain > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Ain Vagula wrote: I wrote yesterday that sdf file must be generated with new toolkit that does not create your language rows (with english strings) for untranslated strings in sdf. You should create sdf file from po files you had before merging m148 or m147-update. ain OK, I gone back and I managed to create the po files from sdf file. And I merged it with latest m148. Thanks. Vlado - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Ain Vagula wrote: > Following steps are needed when migrating to UI strings with no duplicates: > - install updated toolkit > - generate sdf file from your existing translated or half-translated > po-s with new toolkit (to avoid english strings in untranslated > entries) > - backup old po-s somewhere > - generate new set of po-files from just generated sdf-file for your language > - update generated po-files with latest pot-files. > Now every duplicated string in one file has unique identifier, but > string itself is translated as it was in your old po-file. > Note that: > - When you do not regenerate po files, all duplicate entries will be > untranslated. > - When you use sdf file, generated with old toolkit, for regenerating, > untranslated entries will be filled with english strings > > ain thanks Ain, this procedure works like a charm :-) Robert Ludvik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
dwb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vladimir, I had the same problem when I installed the new toolkit alongside the old one in my home directory as per Pavel's blog. I solved it by installing the new toolkit over the old one using the installation method described on the translate web site (root installation). After this everything worked fine. I installed with root installation from the start. This isn't the problem with me. I give up, I tried every possible combination and still getting the empty po files. Can somebody do me a favor, and create the po files from our m147 sdf file located here http://vladoboss.softver.org.mk/wp-uploads/prevodi/GSI_mk.sdf.bz2 and send me bziped po files back to my email? The command should be (according to Pavel blog) oo2po -i GSI_mk.sdf -o po/ -l mk Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
2006/1/6, Vladimir Stefanov <[EMAIL PROTECTED]>: > dwb wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Vladimir, > > > > I had the same problem when I installed the new toolkit alongside the old > > one in my home directory as per Pavel's blog. I solved it by installing the > > new toolkit over the old one using the installation method described on the > > translate web site (root installation). After this everything worked fine. > > > > I installed with root installation from the start. This isn't the > problem with me. I give up, I tried every possible combination and still > getting the empty po files. Can somebody do me a favor, and create the > po files from our m147 sdf file located here > http://vladoboss.softver.org.mk/wp-uploads/prevodi/GSI_mk.sdf.bz2 > and send me bziped po files back to my email? > The command should be (according to Pavel blog) > oo2po -i GSI_mk.sdf -o po/ -l mk > Thanks in advance > I could create po files successfully, I'll upload these after some minutes to http://linux.ee/~vagula/mk.tar.bz2 ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vladimir, I had the same problem when I installed the new toolkit alongside the old one in my home directory as per Pavel's blog. I solved it by installing the new toolkit over the old one using the installation method described on the translate web site (root installation). After this everything worked fine. Good luck David. Vladimir Stefanov wrote: > I merged m145 and m147 po files with old translate toolkit. When I tried > to update to the new toolkit RC5 I got empty .po files. I used this comand: > oo2po -i GSI_mk.sdf -o po/ -l mk > and I got this errors: > oo2po: warning: Error processing: input xmlsecurity/source/component.oo, > output po/xmlsecurity/source/component.po, template None: list index out > of range > [###] 25% > oo2po: warning: Error processing: input svx/source/svdraw.oo, output > po/svx/source/svdraw.po, template None: list index out of range -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDvjsdgH46HTEjeiURAjU/AKCwVpfFak0HiAgPkzPAg0OxdH+4qwCgvG04 mMFLEjdGGQ3SGGkwkWs3O/c= =/JMT -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Ain Vagula wrote: You did not read Pavel's comments about upgrading translate-toolkit version? http://blog.janik.cz/archives/2005/12/25/T18_32_59/ and thread in this list "Updating translate toolkit" ain I merged m145 and m147 po files with old translate toolkit. When I tried to update to the new toolkit RC5 I got empty .po files. I used this comand: oo2po -i GSI_mk.sdf -o po/ -l mk and I got this errors: oo2po: warning: Error processing: input xmlsecurity/source/component.oo, output po/xmlsecurity/source/component.po, template None: list index out of range [###] 25% oo2po: warning: Error processing: input svx/source/svdraw.oo, output po/svx/source/svdraw.po, template None: list index out of range [###] 25% oo2po: warning: Error processing: input sw/source/ui/docvw.oo, output po/sw/source/ui/docvw.po, template None: list index out of range [###] 26% oo2po: warning: Error processing: input sw/source/ui/wrtsh.oo, output po/sw/source/ui/wrtsh.po, template None: list index out of range. So I suppose this is the problem why now I get all this untranslated messages. Can anyone told me how to get properly .po files from GSI_mk.sdf file? Cheers Vlado - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Robert Ludvik wrote: > I ran oo2po from new translate-toolkit-0.8rc5 last day and found out pot2po, sorry. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
2006/1/5, Robert Ludvik <[EMAIL PROTECTED]>: > Vladimir Stefanov wrote: > > Hi > > I merged m147 with m148 and to my surprise I found 2327 new untranslated > > messages (in UI only, not in help content)! Is this true or something > > has gone wrong during merging, because in m147 UI was 100% translated? > > Maybe this has something to do with 'new format' (see > http://blog.janik.cz/archives/2005/12/25/T18_32_59/)? > I ran oo2po from new translate-toolkit-0.8rc5 last day and found out > that there were many untranslated strings in m148 but didn't analyse yet... > Robert Ludvik > Following steps are needed when migrating to UI strings with no duplicates: - install updated toolkit - generate sdf file from your existing translated or half-translated po-s with new toolkit (to avoid english strings in untranslated entries) - backup old po-s somewhere - generate new set of po-files from just generated sdf-file for your language - update generated po-files with latest pot-files. Now every duplicated string in one file has unique identifier, but string itself is translated as it was in your old po-file. Note that: - When you do not regenerate po files, all duplicate entries will be untranslated. - When you use sdf file, generated with old toolkit, for regenerating, untranslated entries will be filled with english strings ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
Vladimir Stefanov wrote: > Hi > I merged m147 with m148 and to my surprise I found 2327 new untranslated > messages (in UI only, not in help content)! Is this true or something > has gone wrong during merging, because in m147 UI was 100% translated? Maybe this has something to do with 'new format' (see http://blog.janik.cz/archives/2005/12/25/T18_32_59/)? I ran oo2po from new translate-toolkit-0.8rc5 last day and found out that there were many untranslated strings in m148 but didn't analyse yet... Robert Ludvik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
On 13:11, Thu 05.01.06, Vladimir Stefanov wrote: Hi I merged m147 with m148 and to my surprise I found 2327 new untranslated messages (in UI only, not in help content)! Is this true or something has gone wrong during merging, because in m147 UI was 100% translated? Something wrong with your merge. There is ~20 new/updated messages in UI. Maybe you switched from old style PO (with merged duplicates) to new style (with separated duplicates and KDE style comments)? -- Best regards, Rail Aliev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] m148
2006/1/5, Vladimir Stefanov <[EMAIL PROTECTED]>: > Hi > I merged m147 with m148 and to my surprise I found 2327 new untranslated > messages (in UI only, not in help content)! Is this true or something > has gone wrong during merging, because in m147 UI was 100% translated? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > You did not read Pavel's comments about upgrading translate-toolkit version? http://blog.janik.cz/archives/2005/12/25/T18_32_59/ and thread in this list "Updating translate toolkit" ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] m148
Hi I merged m147 with m148 and to my surprise I found 2327 new untranslated messages (in UI only, not in help content)! Is this true or something has gone wrong during merging, because in m147 UI was 100% translated? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
