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]
