[Scilab-loc] Re: Opinions on the localization of the help pages

[Kenneth Nielsen]

2011/5/18 Sylvestre Ledru <sylvestre.ledru at scilab.org>:
> Le samedi 14 mai 2011 à 23:13 +0200, Kenneth Nielsen a écrit :
>> Hey
>>
>> > Hi!
>> >
>> > It seems that it will be problematic to make the full translation during
>> > the next release cycle.
>> >
>> > On the other hand po2xml generates docbook only for 100% translated PO
>> > that is 100% XML-compliant.
>> > It is good for consistency, but Rosetta do not check the XML (it is well
>> > known that Ubuntu docs are broken for many languages because the
>> > translators ignore the guidelines or use the wrong guidelines). In KDE we
>> > use pology+Lokalize to debug POs with XML code, but it can be the overkill
>> > for Scilab.
>>
>> Alternatively you can also use gtxml (GetTextXML) from the pyg3t
>> package (of which I'm a co-author, this is really just shameless
>> adverticement ;)). gtxml is written by a fellow Danish translator Ask
>> H. Larsen. It is a commandline tool that generates helpful error
>> messages, so it can be used e.g. for checking the xml of all the
>> localised files and sending out a combined email with errors for all
>> of them.
> Do you have some documents and use cases of it ?

Unfortunately not. The only documentation at the time is what is in
the --help function:
Usage: gtxml [OPTION]... [FILE]...

Parse the contents of each po-FILE, writing warnings for entries suspected of
containing ill-formed xml.  A translated entry is considered ill-formed if its
msgid is well-formed xml while at least one of its msgstrs is not.  If no FILE
is given, or if FILE is -, read from stdin.

Options:
  --version      show program's version number and exit
  -h, --help     show this help message and exit
  -s, --summary  write only whether each FILE passes or fails, and the number
                 of valid and invalid strings for each file.
  -f, --fuzzy    print warnings for fuzzy entries aside from just translated
                 entries.

As for use cases I can provide you with some if you like, but as you
can see from the above it is pretty simple.

As I said earlier, pyg3t is still a relatively young project, so it
would be probably be ok to use for generating warnings that could be
sent to an email list, but I would probably be a little hesitant of
using it for build time checks at this point. At least you should
know, that if you do, you will be the first ones.

Regards Kenneth