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]

Reply via email to