On Thu, May 11, 2006 at 03:33:02PM +0200, Michael Van Canneyt wrote:
> I didn't say 'possible', I said 'suitable'.
>
> Looking at the website:
>
> I think the po2xml is just used to translate the program strings which
> appear in the
> docs (used to refer to button captions etc), not for the actual
> documentation text.
>
> Changing 1 letter in the documentation text would completely kill your
> po2xml
> output, since it is based on textual search.
Ok, I see. But for my experience in translation, having a revision
control like that offered by the gettext/po file, for multilingual
translation is really paramount.
And .po strings are not limited in size so they can easily fit in
the paragraph size for documentation source.
During the translation of some big GPL programs I found that all pages
of the manual are divided in paragraph size chunks, suiteable for .po strings
substitution/upgrade.
The update/upgrade process and the inherently interesting features needed are
the
most important factor here.
The use of .po files is IMHO a really A VERY COOL thing for a multilanguage
manual, especially if you plan to translate it and in the meantime it grows
up...
Then the gettext utility programs comes really useful and I cannot see
any other intrument able to manage such things as good as the gettext
suite (and the so many .po files editors are really something).
For example I use emacs in po-mode but I know of many vi (gosh) users
too.
--
Marco Ciampa
+--------------------+
| Linux User #78271 |
| FSFE fellow #364 |
+--------------------+
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
