Tímár András wrote:
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.
Latest translate-tools can operate so, that all strings in one po file
are unique (using kde-style identifier in msgid).
(Seems too be default behaviour even).
I switched over about month ago, no problems.
I just created new po-files from translated gsi, so I preserved all
existing translations.
Now I generate with every milestone pot files myself, from en_US.sdf
that Pavel provides with his pot files. I think it is more logical even
- team gives us sdf file and we give sdf file back. It is not
complicated in any way, only one command and 2 minutes more by nl team
worker.
ain
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
