Hi Julien,
Julien Lepiller <julien@lepiller.eu> skribis:
Toggle quote (12 lines)
> The attached patch adds a new section to the manual (and therefore
> should wait for the next release since we are in string freeze) that
> documents the translation process for contributors.
>
> From ce110d021935467753e0086c6992c45bf9a48388 Mon Sep 17 00:00:00 2001
> From: Julien Lepiller <julien@lepiller.eu>
> Date: Wed, 14 Apr 2021 00:16:01 +0200
> Subject: [PATCH] doc: Document translation process.
>
> doc/contributing.texi (Translating Guix): New section.
> doc/guix.texi (Top): Add a reference to the new section.
Excellent!
I have little to say, just some cosmetic comments:
Toggle quote (3 lines)
> +The manual and the cookbook both use texinfo. As for @code{packages}, please
> +keep texinfo markup as is. There are more possible markup types in the manual
s/texinfo/Texinfo/ (throughout)
Toggle quote (7 lines)
> +@subsubheading Outside of Weblate
> +
> +Currently, some parts of Guix cannot be translated on Weblate, help wanted!
> +
> +@itemize
> +@item Guix pull news can be translated in @file{news.scm}, but is not
s/Guix pull/@command{guix pull}
Toggle quote (5 lines)
> + available from Weblate. If you want to provide a translation, you
> + can prepare a patch as described above, or simply send us your
> + translation with the name of the news entry your translate and your
> + language.
Maybe add: “@xref{Writing Channel News}, for more information about
channel news.”
Toggle quote (2 lines)
> +@item Guix blog posts cannot currently be translated.
Since it’s Markdown, would po4a work for them?
Toggle quote (4 lines)
> +@item Some of the libraries Guix cannot be translated or are translated outside
> + of the Guix project. Guile itself does not provide a translation
> + mechanism.
A word is missing from the first sentence. You mean that Guile itself
and some of the libraries Guix relies on are not internationalized,
right?
Thanks for taking the time to document all this!
Ludo’.
