GNU bug report logs - #47763
[PATCH] doc: Document translation process.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47763 in the body.
You can then email your comments to 47763 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: guix-patches <at> gnu.org
Subject: [PATCH] doc: Document translation process.
Date: Wed, 14 Apr 2021 00:48:57 +0200

[Message part 1 (text/plain, inline)]

Hi Guix!

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.

[0001-doc-Document-translation-process.patch (text/x-patch, attachment)]

Message #8 received at 47763 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 47763 <at> debbugs.gnu.org
Subject: Re: bug#47763: [PATCH] doc: Document translation process.
Date: Fri, 16 Apr 2021 23:08:41 +0200

Hi Julien,

Julien Lepiller <julien <at> lepiller.eu> skribis:

> 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 <at> 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:

> +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)

> +@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}

> +      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.”

> +@item Guix blog posts cannot currently be translated.

Since it’s Markdown, would po4a work for them?

> +@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’.

Message #13 received at 47763-done <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 47763-done <at> debbugs.gnu.org
Subject: Re: bug#47763: [PATCH] doc: Document translation process.
Date: Sun, 25 Apr 2021 16:04:13 +0200

Le Fri, 16 Apr 2021 23:08:41 +0200,
Ludovic Courtès <ludo <at> gnu.org> a écrit :

> Hi Julien,
> 
> Julien Lepiller <julien <at> lepiller.eu> skribis:
> 
> > 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 <at> 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:
> 
> > +@item Guix blog posts cannot currently be translated.  
> 
> Since it’s Markdown, would po4a work for them?

Indeed, it should be pretty easy, but the question is how to integrate
that process with weblate and the website (how to link an article to
its translations automatically, etc).

> 
> > +@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?

I changed the sentence to say that, thanks :)

> 
> Thanks for taking the time to document all this!
> 
> Ludo’.

I pushed a slightly extended version after I fixed your remarks as
1897a6efa77e341a091e40140d02b525eabb3fdf. Thank you!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.