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

Kenneth Nielsen k.nielsen81 at gmail.com
Sat May 14 23:16:03 CEST 2011


2011/5/14 Kenneth Nielsen <k.nielsen81 at gmail.com>:
> 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.
>
>> Thus, The following questions have to be answered:
>>
>> 1. The improper POs can be excluded from docbook generation, but how to
>> send the message with the errors to the translators?
>
> gtxml could produce the errors, the communication is a bit more
> tricky. It might also be hooked in a build script to exclude broken
> files at build time, but I guess maybe the proper way to fix the

Uhh I forgot to say that this has never been done though. It is a
relatively new tool.

> problem, is to do the check as a commit hook, so the bad files never
> make it in the source tree.
>
> Regards Kenneth
>
>> 2. To generate docbooks from the partial translation we can modify po2xml
>> (patches can be found in kde-i18n-doc, I can give the links if needed) or
>> use po4a (it seems to me that in this case it will be also better to use
>> po4a for generate POTs generation). So what the proper level of the
>> translation to include it into the release?
>>
>> 3. If there is no translation English docbook should be shown. Is this
>> feasible?
>>
>> If these issues can be solved, I think there are no other obstacles to
>> make the docs translatable.
>>
>> Thanks in advance for the answers.
>>
>> Best regards,
>> Yuri
>>
>> ________________________________
>> View this message in context: Re: Opinions on the localization of the help
>> pages
>> Sent from the Scilab localization - Mailing Lists Archives mailing list
>> archive at Nabble.com.
>>
>



More information about the localization mailing list