Pavel Janík wrote:
From: Tímár András <[EMAIL PROTECTED]>
Date: Thu, 06 Oct 2005 16:10:09 +0200
> In Hungarian we have similar problems like Hristo has. "Left" can be
> "Bal", "Balra", "Bal oldali" etc. depending on context. PO file format
> cannot handle this.
This is not true. This is the limitation of the current translate tools. We
plan to update just after the release of 2.0 to prevent problems with the
release. Ain is actively working on testing new translate toolkit.
Ok, I'm trying to work with this. It lacks some things, that are
mentioned in oo2po.py as TODO (some switches), but in general it is
usable, at least I have not seen any mistakes, caused by these scripts.
I use:
- oo2po from cvs version of tools for generating pot's (
/home/ain/bin/oo2po -i /home/ain/ooocvs/et/en-US.sdf -o
/home/ain/ooocvs/et/pot/ -P )
This ads by default unique ID to all repeating strings in ONE pot file.
- your POT2PO for merging
- po2oo from tools for backconversion.
For generating my first po files from old translation (id est, sdf file
generated with previous toolkit) I used command:
/whatever/oo2po -i /mydir/GSI_et.sdf1 -o /mydir/PO/ -l et
(without -P option)
Starting the translation this way is of course stupid - who wants to
translate 500 times strings 'syntax', 'example' etc. in calc help, but
in QA stage is switching to newer tools quite reasonable to get the best
out of your work.
Ain
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
