Hristo Simenov Hristov írta:
> We need unique stringid for every string because we have different 
> translations of one english string. For example in /svx/source/dialog.po for 
> string: ~Left we have three tranlations denepending of usage of that string.
> So, to use such server it have to be fixed po extraction from the source to 
> prevent such problems.

The reason why localizers of free software use PO files, because there
are tools that operate on PO files. However, PO files are not very
suitable for translating GUI not to mention help. If the software uses
gettext, then there is hardly any other option, but if it does not (like
OOo) we should think about alternatives. I believe that it is better to
work with the SDF file as information can be lost when converting GSI to
PO and vice versa.

I wish there was a tool which can operate on SDF file directly. Two
years ago Janos Noll presented such tool at OOoCon2003 in Hamburg. This
tool was far from perfect, but the Hungarian team used it to translate
OOo 1.0 in 3 days. This program has not been maintaned since then. But
the concept could be revived.

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. We had problems with hotkeys. We had problems with
accents (in TableWizard). If I split the segments in the PO file, the
PO->SDF conversion is OK, but I cannot update the files with the
standard gettext commands, because it is illegal to have to identical
msgid's in a PO file.

At http://hu.openoffice.org/source/browse/hu/hu-po-2/ you can check the
4 diff files which I had to apply to the Hungarian SDF file in order to
overcome to the limitations of PO file format. At some point I got tired
of this and since then I work directly on the SDF file. PO files are
evil. You have been warned. ;-)

Andras

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to