-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Nikolai,
On Tuesday 14 September 2004 18:43, Nikolai Prokoschenko wrote:
> Is there any (non-)obvious reason to prefer direct XML-editing over the
> xml2pot way?
No, I would say using po files would be preferred. However, you do need
someone to point you in the right direction :-)
Recently it was also suggested (in the d-doc maillist) that po4a will become
available, but maybe it does not yet have support for SGML.
I have received your information on how to use poxml, and yesterday I did
some tests with it on my Dutch translation. I wrote some scripts to
automatically converted all English .xml files to .pot (using xml2pot) and
all my Dutch translations to .nl.po (using split2po). In general it seems to
work very well.
However, I did encounter a few problems.
- - The preface.xml is not handled correctly by xml2pot: from the <preface>
tag down it is _not_ included in the .pot (attached) and in the .nl.po.
I think this also explains why the first pages of the ru translation are
incomplete.
I guess this should be repported as a bug upstream.
- - xml2pot replaces some text by fairly unreadable codes where the real text
to be translated tends go get lost. See for example the <informalexample>
table in module/partman.pot (attached).
- - When using split2po, the structure of the original and the translation
must be completely equal. Although that is not an error, it is something
to watch out for when converting. I had three files (that I know of) where
the .nl.po was generated incorrectly by split2po:
- preface.xml: I had added a <para> in the Dutch .xml explaning that the
translation is Work in progress;
- boot-new/boot-new.xml: I had chosen not to translate one particular
<para>;
- administrivia/contributors.xml: I had resorted the languages in Dutch.
I don't see very many problems to convert the build system from using .xml
translations to using .ll_CC.po files. I am willing to do this myself.
It should also be quite simple to generate good translation status pages,
showing translated, untranslated and out-of-date (fuzzy); especially as we
can probably build on seppy's current work.
So, all in all, IMHO we are not ready to move all existing translations to
.pot. I _do_ think that we should look into this seriously post-sarge.
Cheers,
FJP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBR0EQgm/Kwh6ICoQRAmrKAJ0eksVWw0pUjMDvJth0Yk8Xzo27ZACeIytO
njCahairmG6z5THlDPvPahw=
=rgbw
-----END PGP SIGNATURE-----
Attachment:
partman.pot
Description: application/gettext
Attachment:
preface.pot
Description: application/gettext