ubuntu-manual team mailing list archive
-
ubuntu-manual team
-
Mailing list archive
-
Message #03434
Re: Compilation of translations
Hey, Carsten.
On Sun, Jul 22, 2012 at 2:39 PM, Carsten Gerlach <daswaldhorn@xxxxxx> wrote:
> This weekend I tried to compile a translated version of the manual. I
> noticed that the names of all translators are automatically exported
> from Launchpad to the *.po files. If you compile the manual with this
> raw list, the you get a ugly result in this section, because of the
> narrow columns and the long user page links.
>
> Therefore I wrote a small script, which converts this list of
> translators to a LaTeX version. I tested it with several languages,
> Dutch, German, Greek, Russian, Slovenian and Spanish. It looks now
> IMHO better. :-)
>
> Only one small issue I do not yet have solved: If the entry of one
> translator is split to two lines in the original po file (for example
> in the Dutch version) the script does not create perfect results. I
> hope, somebody can give me a hint. :-)
>
> I have pushed it to the precise repository [1]. Please test it and
> give me feedback, especially regarding the integration to the Makefile.
The reason the translation credits exist in their own
translationcredits environment is because I had no idea what Launchpad
would dump in there. The translationcredits environment is set up in
such a way that I can modify the formatting of it without impacting
the translations.
I'll take a look at what Launchpad substitutes for the
translation-credits string. If it's something that's easy to parse, I
may be able to coerce LaTeX into parsing it directly, in which case we
wouldn't need the external sed script.
Another possibility is that what Launchpad emits is inconsistent
enough that it will require manual editing by me or the translation
editor. This would be the case if Launchpad is substituting the 'full
name' that some people use on Launchpad. That name may be incomplete
or may not be what that translator wants to appear in the manual.
In any case, thanks for your work; I'll take a look at it.
--Kevin
Follow ups
References