Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Ariel Constenla-Haile arie...@apache.org: On Wed, Mar 28, 2012 at 09:36:11PM +0400, Serg Bormant wrote: 2012/3/28 Claudio Filho filh...@gmail.com: Sorry, Risto. For this step, you need to do: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -o fi.SDF $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ wget http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -O fi.SDF May be it's better to use Apache Subversion to checkout that file: svn co https://svn-master.apache.org/repos/asf/incubator/ooo/trunk/extras/l10n/source/fi Then you can update it, as it get updated by AOO devs.: cd fi svn up Lost wget in second line and -O (upper case o) instead of -o Then you will have the template (en_US) more the old translation (fi) in the same directory, so you can merge in an unique file. $ cat en-US.sdf fi.sdf fi.old.sdf After, convert in PO files. $ oo2po --source-language=en-US -l fi -i fi.old.sdf fi ... and now you get backtrace with ValueError: invalid tab-delimited line: '#\n' This is because of the header comment in the localize.sdf. Copy the file and remove the first 31 lines of the header: cp fi/localize.sdf fi-old.sdf vim fi-old.sdf (remove the comments at the beginning) cat en-US.sdf fi-old.sdf fi-merged.sdf Thanks, header was the source of error, not line in the middle of sdf with literally '#\n' as I mistakenly thought. While the header is 31 line this simple command sequence prepares Russian PO set in ui/ and help/ directories with the same structure as used in pootle l10n projects. $ svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk/extras/l10n/source/ru ru $ wget -O en-US.sdf http://people.apache.org/~jsc/sdf/en-US.sdf $ ( cat en-US.sdf ; tail -n +32 ru/localize.sdf ) merged.sdf $ rm ui help $ oo2po -l ru merged.sdf ui $ mv ui/helpcontent2 ./help To update localized .sdf: $ svn co ru It would be nice to checkout/update en-US.sdf from svn too. What do you think about this? On the one hand, the en-US.sdf is not source file because it is generated based on the source tree, but on the other it is the starting point (and a source) for l10n process. -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
On 3/29/12 8:11 AM, Serg Bormant wrote: Hi 2012/3/28 Ariel Constenla-Hailearie...@apache.org: On Wed, Mar 28, 2012 at 09:36:11PM +0400, Serg Bormant wrote: 2012/3/28 Claudio Filhofilh...@gmail.com: Sorry, Risto. For this step, you need to do: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -o fi.SDF $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ wget http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -O fi.SDF May be it's better to use Apache Subversion to checkout that file: svn co https://svn-master.apache.org/repos/asf/incubator/ooo/trunk/extras/l10n/source/fi Then you can update it, as it get updated by AOO devs.: cd fi svn up Lost wget in second line and -O (upper case o) instead of -o Then you will have the template (en_US) more the old translation (fi) in the same directory, so you can merge in an unique file. $ cat en-US.sdf fi.sdf fi.old.sdf After, convert in PO files. $ oo2po --source-language=en-US -l fi -i fi.old.sdf fi ... and now you get backtrace with ValueError: invalid tab-delimited line: '#\n' This is because of the header comment in the localize.sdf. Copy the file and remove the first 31 lines of the header: cp fi/localize.sdf fi-old.sdf vim fi-old.sdf (remove the comments at the beginning) cat en-US.sdf fi-old.sdf fi-merged.sdf Thanks, header was the source of error, not line in the middle of sdf with literally '#\n' as I mistakenly thought. While the header is 31 line this simple command sequence prepares Russian PO set in ui/ and help/ directories with the same structure as used in pootle l10n projects. $ svn co https://svn.apache.org/repos/asf/incubator/ooo/trunk/extras/l10n/source/ru ru $ wget -O en-US.sdf http://people.apache.org/~jsc/sdf/en-US.sdf $ ( cat en-US.sdf ; tail -n +32 ru/localize.sdf ) merged.sdf $ rm ui help $ oo2po -l ru merged.sdf ui $ mv ui/helpcontent2 ./help To update localized .sdf: $ svn co ru It would be nice to checkout/update en-US.sdf from svn too. What do you think about this? On the one hand, the en-US.sdf is not source file because it is generated based on the source tree, but on the other it is the starting point (and a source) for l10n process. First of all I would like to point you all on this wiki page http://wiki.services.openoffice.org/wiki/Localization_for_developers#Roundtrip You don't have to merge any files together manually. I think in the future we will find a way to checkin the po files instead of the sdf. Or at the beginning we will maybe have both checked in. A goal should be to eliminate the sdf files completely if possible. I can also think about a process where we automatically merge the po files from the pootle into our repo on a regular basis... That means that we would have to update pootle first when we got external offline translated po files or should update both. Juergen
[TRANSLATION]: Steps for update or new translation
Hi 2012/3/27 Anton Meixome meix...@certima.net: What else we can do? Anton, instead of sending an email, i did this page[1] with some informations. Maybe can be more useful that send links of old threads. [1]https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Plan Folks, how we haven't a L10N plan/page, i felt free to write this page. If have errors (that i believe that really have), please, fell free to adjust. If the place isn't the best place, i accept suggestions too. Best, Claudio
Re: [TRANSLATION]: Steps for update or new translation
Hi, as I can see, POT.zip[1] has broken directory structure -- it has no directories at all. [1] https://cwiki.apache.org/confluence/download/attachments/27842653/POT.zip -- wbr, sb среда, 28 марта 2012 г. пользователь Claudio Filho писал: Hi 2012/3/27 Anton Meixome meix...@certima.net javascript:;: What else we can do? Anton, instead of sending an email, i did this page[1] with some informations. Maybe can be more useful that send links of old threads. [1]https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Plan Folks, how we haven't a L10N plan/page, i felt free to write this page. If have errors (that i believe that really have), please, fell free to adjust. If the place isn't the best place, i accept suggestions too. Best, Claudio -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
On 3/28/12 2:30 PM, Claudio Filho wrote: Hi 2012/3/27 Anton Meixomemeix...@certima.net: What else we can do? Anton, instead of sending an email, i did this page[1] with some informations. Maybe can be more useful that send links of old threads. [1]https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Plan Folks, how we haven't a L10N plan/page, i felt free to write this page. If have errors (that i believe that really have), please, fell free to adjust. If the place isn't the best place, i accept suggestions too. did you know this page http://wiki.services.openoffice.org/wiki/Localization_for_developers and http://wiki.services.openoffice.org/wiki/Pootle_User_Guide search in the wiki.servicves.openoffice.org for localization and you will find more. I think we should try collect the information in one place and should consolidate it. Juergen
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Serg Bormant borm...@gmail.com: as I can see, POT.zip[1] has broken directory structure -- it has no directories at all. More or less, Serg. What you need? If is files and directories, ok, it is broken. When you use oo2po[1], you have some options. I started like you said, with *many* dirs/subdirs, but after, i tried too in this way and in one unique file (that is a suicide option, imho). [1]http://translate.sourceforge.net/wiki/toolkit/oo2po From this page[1]: --multifile=MULTIFILESTYLE | how to split po/pot files (single, toplevel or onefile) For this POT files, i used toplevel option. So, if you have a team, is more easy send *one* file per translator. But i will update there page and add a 2nd file with dirs/subdirs. Best, Claudio
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Jürgen Schmidt jogischm...@googlemail.com: did you know this page http://wiki.services.openoffice.org/wiki/Localization_for_developers and http://wiki.services.openoffice.org/wiki/Pootle_User_Guide Humm!! Yes, i know this pages, but was outdated. I saw now that you worked a lot over them. Sorry by my mistake. I think we should try collect the information in one place and should consolidate it. Absolutely. I agree with you, but wasn't clear where to work. Thanks by to clear the question, Jürgen. Best, Claudio
Re: [TRANSLATION]: Steps for update or new translation
Hi, More or less, Serg. What you need? If is files and directories, ok, it is broken. When POT set has the same directory structure as in pootle it can be processed with gettext tools and translate toolkit tools. Result set of POs can be zipped and uploaded to pootle after migrating translation from previous version. When you use oo2po[1], you have some options. I started like you said, with *many* dirs/subdirs, but after, i tried too in this way and in one unique file (that is a suicide option, imho). [1]http://translate.sourceforge.net/wiki/toolkit/oo2po From this page[1]: --multifile=MULTIFILESTYLE | how to split po/pot files (single, toplevel or onefile) Which version of oo2po was used to generate POTs? As for me oo2po from translate-toolkit-1.9.0/python-2.6.6 breaks with diagnostics like: Traceback (most recent call last): File /usr/bin/oo2po, line 27, in module oo2po.main() ... ValueError: invalid tab-delimited line: '#\n' -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
On 3/28/12 4:34 PM, Serg Bormant wrote: Hi, More or less, Serg. What you need? If is files and directories, ok, it is broken. When POT set has the same directory structure as in pootle it can be processed with gettext tools and translate toolkit tools. Result set of POs can be zipped and uploaded to pootle after migrating translation from previous version. When you use oo2po[1], you have some options. I started like you said, with *many* dirs/subdirs, but after, i tried too in this way and in one unique file (that is a suicide option, imho). [1]http://translate.sourceforge.net/wiki/toolkit/oo2po From this page[1]: --multifile=MULTIFILESTYLE | how to split po/pot files (single, toplevel or onefile) Which version of oo2po was used to generate POTs? As for me oo2po from translate-toolkit-1.9.0/python-2.6.6 breaks with diagnostics like: oo2po --version oo2po 1.9.0 What do you need? I can provide a set of po files for you. Juergen Traceback (most recent call last): File /usr/bin/oo2po, line 27, inmodule oo2po.main() ... ValueError: invalid tab-delimited line: '#\n'
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Jürgen Schmidt jogischm...@googlemail.com: oo2po --version oo2po 1.9.0 Thanks. And what about python --version? What do you need? I can provide a set of po files for you. Can you provide POT or PO set with the same directory structure as used for AOO projects on https://translate.apache.org/ru/ ? Thanks. When I tried to pomigrate2 --locale=ru ../ooru/trunk/ui ./ui ./POT with toplevel POT set[1], pocount ui said that less than 1% of early translated messages was migrated: TOTAL: type strings words (source)words (translation) translated: 12 ( 0%) 19 ( 0%) 18 fuzzy: 26 ( 0%) 45 ( 0%) n/a untranslated: 72658 ( 99%) 528304 ( 99%) n/a Total:72696528368 18 ooru/trunk/ui has the same directory structure as AOO project on Apache (and Sun) pootle servers. [1] https://cwiki.apache.org/confluence/download/attachments/27842653/POT.zip -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
On 3/28/12 5:07 PM, Serg Bormant wrote: Hi 2012/3/28 Jürgen Schmidtjogischm...@googlemail.com: oo2po --version oo2po 1.9.0 Thanks. And what about python --version? What do you need? I can provide a set of po files for you. Can you provide POT or PO set with the same directory structure as used for AOO projects on https://translate.apache.org/ru/ ? Thanks. yes I can and will do it later ... I have updated the Pootle server and I am still updating the help project ... UI For the UI we have a straight forward directory structure that is equal to the pot directory structure that you get from the en-US.sdf file using oo2po ... Help In the current help project we have cut the helpcontent2 directory and start with source. The only advantage I see here is the shorter path. But it makes things more complicate for updates... Anyway we will change this in the future. The file http://people.apache.org/~jsc/sdf/aoo34_pot_templates.tar.bz2 contains the latest pot files (including) helpcontent2. Simply move helpcontent2 in a separate directory and use the source only for your help project. For the UI you can use the rest of the template folder. The file http://people.apache.org/~jsc/sdf/en-US.sdf contains the latest resource strings that are used as base for the new templates. po files ru will I zip later together for you. Juergen PS: please be patient with the help project until I have completed the update. Only few languages left. When I tried to pomigrate2 --locale=ru ../ooru/trunk/ui ./ui ./POT with toplevel POT set[1], pocount ui said that less than 1% of early translated messages was migrated: TOTAL: type strings words (source)words (translation) translated: 12 ( 0%) 19 ( 0%) 18 fuzzy: 26 ( 0%) 45 ( 0%) n/a untranslated: 72658 ( 99%) 528304 ( 99%) n/a Total:72696528368 18 ooru/trunk/ui has the same directory structure as AOO project on Apache (and Sun) pootle servers. [1] https://cwiki.apache.org/confluence/download/attachments/27842653/POT.zip
Re: [TRANSLATION]: Steps for update or new translation
Claudio Filho [filh...@gmail.com] kirjoitti: Hi 2012/3/27 Anton Meixome meix...@certima.net: What else we can do? Anton, instead of sending an email, i did this page[1] with some informations. Maybe can be more useful that send links of old threads. [1]https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Plan Folks, how we haven't a L10N plan/page, i felt free to write this page. If have errors (that i believe that really have), please, fell free to adjust. If the place isn't the best place, i accept suggestions too. Best, Claudio I try to follow orders on the page but there was no information where I can find en-US.sdf -file. I find one using google (12 925 584 bytes) I think I succeed to create old.sdf file but then I got this: - ristoi@Uusbuntu ~/AOOWDir $ oo2po --source-language=en-US -l fi -i old.sdf fi Traceback (most recent call last): File /usr/bin/oo2po, line 27, in module oo2po.main() File /usr/lib/python2.7/dist-packages/translate/convert/oo2po.py, line 170, in main parser.run(argv) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 136, in run self.recursiveprocess(options) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 359, in recursiveprocess return super(ArchiveConvertOptionParser, self).recursiveprocess(options) File /usr/lib/python2.7/dist-packages/translate/misc/optrecurse.py, line 495, in recursiveprocess inputfiles = self.recurseinputfiles(options) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 250, in recurseinputfiles options.inputarchive = self.openarchive(options.input, 'input') File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 245, in openarchive return archiveclass(archivefilename, **archiveoptions) File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 341, in __init__ self.createsubfileindex() File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 347, in createsubfileindex subfile = self.getsubfilename(line) File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 356, in getsubfilename raise ValueError(invalid tab-delimited line: %r % line) ValueError: invalid tab-delimited line: '#\n' - There seem to exist no file in Fi directory. I must admit that I use modern OS with GUI (LinuxMint) and those command line tools are not for me. But if there is some easy way to continue here I will try. Greetings Risto
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: I try to follow orders on the page but there was no information where I can find en-US.sdf -file. I find one using google (12 925 584 bytes) I think I succeed to create old.sdf file but then I got this: - ristoi@Uusbuntu ~/AOOWDir $ oo2po --source-language=en-US -l fi -i old.sdf fi Traceback (most recent call last): File /usr/bin/oo2po, line 27, in module oo2po.main() File /usr/lib/python2.7/dist-packages/translate/convert/oo2po.py, line 170, in main parser.run(argv) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 136, in run self.recursiveprocess(options) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 359, in recursiveprocess return super(ArchiveConvertOptionParser, self).recursiveprocess(options) File /usr/lib/python2.7/dist-packages/translate/misc/optrecurse.py, line 495, in recursiveprocess inputfiles = self.recurseinputfiles(options) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 250, in recurseinputfiles options.inputarchive = self.openarchive(options.input, 'input') File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 245, in openarchive return archiveclass(archivefilename, **archiveoptions) File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 341, in __init__ self.createsubfileindex() File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 347, in createsubfileindex subfile = self.getsubfilename(line) File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 356, in getsubfilename raise ValueError(invalid tab-delimited line: %r % line) ValueError: invalid tab-delimited line: '#\n' - There seem to exist no file in Fi directory. I must admit that I use modern OS with GUI (LinuxMint) and those command line tools are not for me. But if there is some easy way to continue here I will try. I got the same result with localized .sdf. Try to use http://people.apache.org/~jsc/sdf/en-US.sdf from Jürgen Schmidt. -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
Serg Bormant [borm...@gmail.com] kirjoitti: Hi 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: I try to follow orders on the page but there was no information where I can find en-US.sdf -file. I find one using google (12 925 584 bytes) I think I succeed to create old.sdf file but then I got this: - ristoi@Uusbuntu ~/AOOWDir $ oo2po --source-language=en-US -l fi -i old.sdf fi Traceback (most recent call last): File /usr/bin/oo2po, line 27, in module oo2po.main() File /usr/lib/python2.7/dist-packages/translate/convert/oo2po.py, line 170, in main parser.run(argv) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 136, in run self.recursiveprocess(options) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 359, in recursiveprocess return super(ArchiveConvertOptionParser, self).recursiveprocess(options) File /usr/lib/python2.7/dist-packages/translate/misc/optrecurse.py, line 495, in recursiveprocess inputfiles = self.recurseinputfiles(options) File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 250, in recurseinputfiles options.inputarchive = self.openarchive(options.input, 'input') File /usr/lib/python2.7/dist-packages/translate/convert/convert.py, line 245, in openarchive return archiveclass(archivefilename, **archiveoptions) File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 341, in __init__ self.createsubfileindex() File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 347, in createsubfileindex subfile = self.getsubfilename(line) File /usr/lib/python2.7/dist-packages/translate/storage/oo.py, line 356, in getsubfilename raise ValueError(invalid tab-delimited line: %r % line) ValueError: invalid tab-delimited line: '#\n' - There seem to exist no file in Fi directory. I must admit that I use modern OS with GUI (LinuxMint) and those command line tools are not for me. But if there is some easy way to continue here I will try. I got the same result with localized .sdf. Try to use http://people.apache.org/~jsc/sdf/en-US.sdf from Jürgen Schmidt. -- wbr, sb Thank you for info but I think I had correct en-US.sdf file in this step: ristoi@Uusbuntu ~/AOOWDir $ cat en-US.sdf fi.sdf old.sdf File fi.sdf was localize.sdf but when it fails I just change name. No help for that. Regards Risto
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: Thank you for info but I think I had correct en-US.sdf file in this step: ristoi@Uusbuntu ~/AOOWDir $ cat en-US.sdf fi.sdf old.sdf File fi.sdf was localize.sdf but when it fails I just change name. No help for that. Simple try this: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ oo2po -l fi en-US.sdf fi Now check ./fi directory for PO set. Does it help? -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Serg Bormant borm...@gmail.com: 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: Thank you for info but I think I had correct en-US.sdf file in this step: ristoi@Uusbuntu ~/AOOWDir $ cat en-US.sdf fi.sdf old.sdf File fi.sdf was localize.sdf but when it fails I just change name. No help for that. Sorry, Risto. For this step, you need to do: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -o fi.SDF Then you will have the template (en_US) more the old translation (fi) in the same directory, so you can merge in an unique file. $ cat en-US.sdf fi.sdf fi.old.sdf After, convert in PO files. $ oo2po --source-language=en-US -l fi -i fi.old.sdf fi This command will extract the msgid from en-US part and msgstring from fi part. When one or other haven't its pair, return a error, jumping the file. The new created dir called fi will be your TM. So, get the POT files and run the automatic translation, if your translate tool have this feature. At final, is revise what are marks as fuzzy and fill what is empty. Best, Claudio
Re: [TRANSLATION]: Steps for update or new translation
Serg Bormant [borm...@gmail.com] kirjoitti: Hi 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: Thank you for info but I think I had correct en-US.sdf file in this step: ristoi@Uusbuntu ~/AOOWDir $ cat en-US.sdf fi.sdf old.sdf File fi.sdf was localize.sdf but when it fails I just change name. No help for that. Simple try this: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf This create file en-US.sdf.1 It seem to be quite same than what I already had. $ oo2po -l fi en-US.sdf fi I got lot of lines, here last ones: --- Warning: targetlanguage 'fi' not found in inputfile 'helpcontent2/source/text/scalc/guide.oo' (contains en-US) Warning: targetlanguage 'fi' not found in inputfile 'padmin/source.oo' (contains en-US) [###] 100% Now check ./fi directory for PO set. Does it help? Yes there is many directories and maybe all .po files with 0% translations -- wbr, sb Regards Risto
Re: [TRANSLATION]: Steps for update or new translation
2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: $ oo2po -l fi en-US.sdf fi I got lot of lines, here last ones: --- Warning: targetlanguage 'fi' not found in inputfile 'helpcontent2/source/text/scalc/guide.oo' (contains en-US) Warning: targetlanguage 'fi' not found in inputfile 'padmin/source.oo' (contains en-US) [###] 100% Yes, what is natural. It happens because haven't the pair msgid/msgstr, or in other words, have only a msgid from en without a pair in fi, or haven't msgid in en for a msgstr in fi. It is ok only when oo2po find a msgid in en with its msgstr in fi, creating the pair. Claudio
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Claudio Filho filh...@gmail.com: Sorry, Risto. For this step, you need to do: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -o fi.SDF $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ wget http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -O fi.SDF Lost wget in second line and -O (upper case o) instead of -o Then you will have the template (en_US) more the old translation (fi) in the same directory, so you can merge in an unique file. $ cat en-US.sdf fi.sdf fi.old.sdf After, convert in PO files. $ oo2po --source-language=en-US -l fi -i fi.old.sdf fi ... and now you get backtrace with ValueError: invalid tab-delimited line: '#\n' If you don't use content of localized .sdf oo2po does the task. It is the time to migrate old translate to empty PO set now. -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
Claudio Filho [filh...@gmail.com] kirjoitti: Hi 2012/3/28 Serg Bormant borm...@gmail.com: 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: Thank you for info but I think I had correct en-US.sdf file in this step: ristoi@Uusbuntu ~/AOOWDir $ cat en-US.sdf fi.sdf old.sdf File fi.sdf was localize.sdf but when it fails I just change name. No help for that. Sorry, Risto. For this step, you need to do: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -o fi.SDF Then you will have the template (en_US) more the old translation (fi) in the same directory, so you can merge in an unique file. $ cat en-US.sdf fi.sdf fi.old.sdf After, convert in PO files. $ oo2po --source-language=en-US -l fi -i fi.old.sdf fi This command will extract the msgid from en-US part and msgstring from fi part. When one or other haven't its pair, return a error, jumping the file. The new created dir called fi will be your TM. So, get the POT files and run the automatic translation, if your translate tool have this feature. At final, is revise what are marks as fuzzy and fill what is empty. Best, Claudio No I am enought confused. I just deleted whole directory. And start over. I got this: Tiedostoa tai hakemistoa ei ole -o: komentoa ei löydy Maybe it's better I stop using terminal. It is too ancient for me. Regards Risto
Re: [TRANSLATION]: Steps for update or new translation
Hi gsicheck was used for .sdf checking: http://wiki.services.openoffice.org/wiki/Gsicheck http://ooo.services.openoffice.org/gsicheck/ Second link (link to download gsicheck) is broken now. -- wbr, sb
Re: [TRANSLATION]: Steps for update or new translation
Hi 2012/3/28 Risto Jääskeläinen rjaas...@saunalahti.fi: Maybe it's better I stop using terminal. It is too ancient for me. :-) I did a TM in PO format for you, from old fi.sdf. Now, is use POT files and to fill with this TM in an automated process. I think that you will fill ~85% of all. Best, Claudio
Re: [TRANSLATION]: Steps for update or new translation
Hi *, On Wed, Mar 28, 2012 at 09:36:11PM +0400, Serg Bormant wrote: Hi 2012/3/28 Claudio Filho filh...@gmail.com: Sorry, Risto. For this step, you need to do: $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -o fi.SDF $ wget http://people.apache.org/~jsc/sdf/en-US.sdf $ wget http://svn.apache.org/viewvc/incubator/ooo/trunk/extras/l10n/source/fi/localize.sdf?revision=1229431view=co -O fi.SDF May be it's better to use Apache Subversion to checkout that file: svn co https://svn-master.apache.org/repos/asf/incubator/ooo/trunk/extras/l10n/source/fi Then you can update it, as it get updated by AOO devs.: cd fi svn up Lost wget in second line and -O (upper case o) instead of -o Then you will have the template (en_US) more the old translation (fi) in the same directory, so you can merge in an unique file. $ cat en-US.sdf fi.sdf fi.old.sdf After, convert in PO files. $ oo2po --source-language=en-US -l fi -i fi.old.sdf fi ... and now you get backtrace with ValueError: invalid tab-delimited line: '#\n' This is because of the header comment in the localize.sdf. Copy the file and remove the first 31 lines of the header: cp fi/localize.sdf fi-old.sdf vim fi-old.sdf (remove the comments at the beginning) cat en-US.sdf fi-old.sdf fi-merged.sdf Regards -- Ariel Constenla-Haile La Plata, Argentina pgpsn4X5IO2bV.pgp Description: PGP signature
