Re: [l10n-dev] OmegaT and PO files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Helary ha scritto: > > On 19 juin 07, at 17:12, Alessandro Cattelan wrote: >> I don't understand why you need to create .pot instead of .po files. I >> converted the sdf to po files and OmegaT just ignores the msgstr >> content, so what is the use of having a pot file with empty msgstr >> fields? > > Because I am pretty sure OmegaT would not overwrite the msgstr part > since it does not know about it. So this is likely to result in a buggy > target file. But maybe I am just too careful. I've checked the target files and it seems to me that they have been properly compiled by OmegaT: the original msgstr content has been replaced by my translation. Ale. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeEtgdpk3ZlYYJ+gRAth9AJ9NL3LHPqXa2Yw6EYHJlLB36txBhwCfRBDM oAiOCVKjkyuf7P8cgRRe3Ls= =oh8r -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
Thank you Alessandro... Best, Charles. Alessandro Cattelan a écrit : > Charles-H. Schulz ha scritto: > > Hi, > > > sorry this is a side question, as I'm trying to understand the way to > > work with OmegaT and how we end up enriching / easing the localization > > processes. > > What exactly is translation memory and TMX and how do they work? > > > Thank you, > > > Charles. > > > It's all here: > http://en.wikipedia.org/wiki/Translation_memory > > Translation memory is a technology widely used in the professional > translation market: it speeds up the translation process and allows for > a better quality and consistency in translation. > > > > Ale. > - 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] OmegaT and PO files
On 19 juin 07, at 19:51, Rafaella Braconi wrote: yes, I was also suggesting jean-Christophe to use that tmx files but I think that he really want to make sure to get the most updated tmx files... I am currently loading them and I don't see anything problematic. Are you referring to the tmx TEST file I just provided? Does this really work? Yes, I am replying to you offlist with some specifics but basically they work well. JC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
Hi Jean-Christophe, Jean-Christophe Helary wrote: On 19 juin 07, at 18:17, Rafaella Braconi wrote: Hi Alessandro, Jean-Christophe, Alessandro Cattelan wrote: Jean-Christophe Helary ha scritto: I think Rafaella should be able to provide you with proper TMX files that match the .sdf contents. Rafaella has already provided us with the OLH TMX some time ago. yes, I was also suggesting jean-Christophe to use that tmx files but I think that he really want to make sure to get the most updated tmx files... I am currently loading them and I don't see anything problematic. Are you referring to the tmx TEST file I just provided? Does this really work? Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles-H. Schulz ha scritto: > Hi, > > sorry this is a side question, as I'm trying to understand the way to > work with OmegaT and how we end up enriching / easing the localization > processes. > What exactly is translation memory and TMX and how do they work? > > Thank you, > > Charles. > It's all here: http://en.wikipedia.org/wiki/Translation_memory Translation memory is a technology widely used in the professional translation market: it speeds up the translation process and allows for a better quality and consistency in translation. Ale. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGd7KDdpk3ZlYYJ+gRAtDNAJ0SDuNaN9GdfUWDQFcoebDdwI/o7gCfeKUZ mcqlqIyW6Y9pTwN3ekygbJg= =imVs -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
Hi, sorry this is a side question, as I'm trying to understand the way to work with OmegaT and how we end up enriching / easing the localization processes. What exactly is translation memory and TMX and how do they work? Thank you, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
On 19 juin 07, at 17:12, Alessandro Cattelan wrote: I don't understand why you need to create .pot instead of .po files. I converted the sdf to po files and OmegaT just ignores the msgstr content, so what is the use of having a pot file with empty msgstr fields? Because I am pretty sure OmegaT would not overwrite the msgstr part since it does not know about it. So this is likely to result in a buggy target file. But maybe I am just too careful. JC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
On 19 juin 07, at 18:17, Rafaella Braconi wrote: Hi Alessandro, Jean-Christophe, Alessandro Cattelan wrote: Jean-Christophe Helary ha scritto: I think Rafaella should be able to provide you with proper TMX files that match the .sdf contents. Rafaella has already provided us with the OLH TMX some time ago. yes, I was also suggesting jean-Christophe to use that tmx files but I think that he really want to make sure to get the most updated tmx files... I am currently loading them and I don't see anything problematic. The only problem I see with the method you propose is that we would end up having two TM. The TM I have is pretty big (over 12MB) and OmegaT takes a long time to analyse it. If I put another big TM in the tm folder I think it would end up being too slow. However, I'll have a look at that. I am not clear about this. Why would you end up having 2 TMs? Cannot one sinply use the most recent tMX files? Anyway, as far as OmegaT is concerned that does not matter. It is only the total number of segments to match that will lengthen he load process. I have just loaded the 8000 segments + 2 x 2000 segments TMXs matching to the whole .sdf->pot file and it took less than 2mn on my machine (MacBook duo core 2ghz/2gb) I also assigned 2gb to OmegaT -in Java seerver mode (faster in general): java -server -Xmx2048M -jar OmegaT.jar JC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
Hi Alessandro, Jean-Christophe, Alessandro Cattelan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Helary ha scritto: Basically OmegaT's PO handling is only (just like for monolingual files) to put in the target editing field the contents of source, for edition. OmegaT is not able to know that a target already exist and to propose it for editing. What I have thus done is the following: 1) convert the .sdf file to .pot (oo2po -P etc) to remove all the msgstr contents 2) create a TMX from the pseudo translated .sdf (oo2po and then po2tmx, cf my comments on that process in a different thread) 3) put the .pot in /source/, the tmx in /tm/ and OmegaT will automatically match the .pot strings to their pseudo translated counterparts in the tmx, thus allowing you to have the msgstr contents in target. It is a little non-trivial, but remember that OmegaT is not made to work with bilingual localization files. It works with a monolingual file in source and bilingual TM files for reference. I think Rafaella should be able to provide you with proper TMX files that match the .sdf contents. Rafaella has already provided us with the OLH TMX some time ago. yes, I was also suggesting jean-Christophe to use that tmx files but I think that he really want to make sure to get the most updated tmx files... The only problem I see with the method you propose is that we would end up having two TM. The TM I have is pretty big (over 12MB) and OmegaT takes a long time to analyse it. If I put another big TM in the tm folder I think it would end up being too slow. However, I'll have a look at that. I am not clear about this. Why would you end up having 2 TMs? Cannot one sinply use the most recent tMX files? Rafaella I don't understand why you need to create .pot instead of .po files. I converted the sdf to po files and OmegaT just ignores the msgstr content, so what is the use of having a pot file with empty msgstr fields? Ale. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGd4/udpk3ZlYYJ+gRAksmAKDIwVSahA9STieJZ6hI/AklQreOPACgwWTI GmkkHUh4ZZsWkO1b9p2NBGg= =yOoO -END PGP SIGNATURE- - 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] OmegaT and PO files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Helary ha scritto: > Basically OmegaT's PO handling is only (just like for monolingual files) > to put in the target editing field the contents of source, for edition. > > OmegaT is not able to know that a target already exist and to propose it > for editing. > > What I have thus done is the following: > > 1) convert the .sdf file to .pot (oo2po -P etc) to remove all the msgstr > contents > 2) create a TMX from the pseudo translated .sdf (oo2po and then po2tmx, > cf my comments on that process in a different thread) > 3) put the .pot in /source/, the tmx in /tm/ and OmegaT will > automatically match the .pot strings to their pseudo translated > counterparts in the tmx, thus allowing you to have the msgstr contents > in target. > > It is a little non-trivial, but remember that OmegaT is not made to work > with bilingual localization files. It works with a monolingual file in > source and bilingual TM files for reference. > > I think Rafaella should be able to provide you with proper TMX files > that match the .sdf contents. Rafaella has already provided us with the OLH TMX some time ago. The only problem I see with the method you propose is that we would end up having two TM. The TM I have is pretty big (over 12MB) and OmegaT takes a long time to analyse it. If I put another big TM in the tm folder I think it would end up being too slow. However, I'll have a look at that. I don't understand why you need to create .pot instead of .po files. I converted the sdf to po files and OmegaT just ignores the msgstr content, so what is the use of having a pot file with empty msgstr fields? Ale. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGd4/udpk3ZlYYJ+gRAksmAKDIwVSahA9STieJZ6hI/AklQreOPACgwWTI GmkkHUh4ZZsWkO1b9p2NBGg= =yOoO -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
On 19 juin 07, at 15:50, Alessandro Cattelan wrote: Now I have one more question to which I'm sure Jean-Cristophe has the answer... ;o) When opening a project with OmegaT I thought that the text in msgstr in the PO file would show up in the target segment, but that is not the case. I think that checking the PO file si quite useful because of the comments and of the changed strings extracted from the Sun database, but keeping OmegaT and a text editor with the PO file open side by side on a 15' monitor is not very comfortable... Is there any way to make OmT show at least the msgstr content? Yes. It is what I have been demonstrating here by creating a TMX from the .sdf file. Basically OmegaT's PO handling is only (just like for monolingual files) to put in the target editing field the contents of source, for edition. OmegaT is not able to know that a target already exist and to propose it for editing. What I have thus done is the following: 1) convert the .sdf file to .pot (oo2po -P etc) to remove all the msgstr contents 2) create a TMX from the pseudo translated .sdf (oo2po and then po2tmx, cf my comments on that process in a different thread) 3) put the .pot in /source/, the tmx in /tm/ and OmegaT will automatically match the .pot strings to their pseudo translated counterparts in the tmx, thus allowing you to have the msgstr contents in target. It is a little non-trivial, but remember that OmegaT is not made to work with bilingual localization files. It works with a monolingual file in source and bilingual TM files for reference. I think Rafaella should be able to provide you with proper TMX files that match the .sdf contents. Cheers, JC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 F Wolff ha scritto: > On Di, 2007-06-19 at 07:56 +0200, Alessandro Cattelan wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> The first segment that OmegaT opens for every PO file is the following: >> >> "Project-Id-Version: PACKAGE VERSION\n" >> "Report-Msgid-Bugs-To: >> http://qa.openoffice.org/issues/enter_bug.cgi?subcomponent=ui&comment=&short_desc=Localization%20issue%20in%20file%3A%20&component=l10n&form_name=enter_issue\n"; >> "POT-Creation-Date: 2007-06-13 21:53+0200\n" >> "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" >> "Last-Translator: FULL NAME <[EMAIL PROTECTED]>\n" >> "Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n" >> "MIME-Version: 1.0\n" >> "Content-Type: text/plain; charset=UTF-8\n" >> "Content-Transfer-Encoding: 8bit\n" >> "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" >> "X-Generator: Translate Toolkit 0.10.1\n" >> "X-Accelerator-Marker: ~\n" >> >> >> I think nothing needs to be changed here, right? It seems to me those >> are all optional information for project management. The only thing I'm >> not sure about is the Plural-Forms field: does that need to be edited >> anyhow? >> >> Thanks, >> Ale. > > The Plural-Forms header entry is part of the gettext library (the > library that designed the PO format). Nothing in OpenOffice.org will > need or use it, so it can be safely ignored. > > If you use any of the gettext tools on the PO files, they might complain > about that, but I would simply ignore it until then. Thank you, Friedel. Now I have one more question to which I'm sure Jean-Cristophe has the answer... ;o) When opening a project with OmegaT I thought that the text in msgstr in the PO file would show up in the target segment, but that is not the case. I think that checking the PO file si quite useful because of the comments and of the changed strings extracted from the Sun database, but keeping OmegaT and a text editor with the PO file open side by side on a 15' monitor is not very comfortable... Is there any way to make OmT show at least the msgstr content? Ale. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGd3y0dpk3ZlYYJ+gRArTZAJ0StIfyZA+3jrT6Da575cibPvx8HQCgz+um a2NH7a5iMH9XQ//g9dhErXs= =DjVV -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
On Di, 2007-06-19 at 07:56 +0200, Alessandro Cattelan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > The first segment that OmegaT opens for every PO file is the following: > > "Project-Id-Version: PACKAGE VERSION\n" > "Report-Msgid-Bugs-To: > http://qa.openoffice.org/issues/enter_bug.cgi?subcomponent=ui&comment=&short_desc=Localization%20issue%20in%20file%3A%20&component=l10n&form_name=enter_issue\n"; > "POT-Creation-Date: 2007-06-13 21:53+0200\n" > "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" > "Last-Translator: FULL NAME <[EMAIL PROTECTED]>\n" > "Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=UTF-8\n" > "Content-Transfer-Encoding: 8bit\n" > "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" > "X-Generator: Translate Toolkit 0.10.1\n" > "X-Accelerator-Marker: ~\n" > > > I think nothing needs to be changed here, right? It seems to me those > are all optional information for project management. The only thing I'm > not sure about is the Plural-Forms field: does that need to be edited > anyhow? > > Thanks, > Ale. The Plural-Forms header entry is part of the gettext library (the library that designed the PO format). Nothing in OpenOffice.org will need or use it, so it can be safely ignored. If you use any of the gettext tools on the PO files, they might complain about that, but I would simply ignore it until then. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] OmegaT and PO files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The first segment that OmegaT opens for every PO file is the following: "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://qa.openoffice.org/issues/enter_bug.cgi?subcomponent=ui&comment=&short_desc=Localization%20issue%20in%20file%3A%20&component=l10n&form_name=enter_issue\n"; "POT-Creation-Date: 2007-06-13 21:53+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <[EMAIL PROTECTED]>\n" "Language-Team: LANGUAGE <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" "X-Generator: Translate Toolkit 0.10.1\n" "X-Accelerator-Marker: ~\n" I think nothing needs to be changed here, right? It seems to me those are all optional information for project management. The only thing I'm not sure about is the Plural-Forms field: does that need to be edited anyhow? Thanks, Ale. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGd3Aedpk3ZlYYJ+gRAiyJAKDn7WT2i/DUmhg1f16h8okgsbLnZQCeK9md 5vZdPQcyTzeJk7jDdM+ytEg= =KH6Q -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
