all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Translation of the Guix manual & node names
Date: Wed, 24 Apr 2019 00:45:53 +0200	[thread overview]
Message-ID: <87d0lce3xa.fsf@gnu.org> (raw)
In-Reply-To: <20190423155219.03d067f5@sybil.lepiller.eu> (Julien Lepiller's message of "Tue, 23 Apr 2019 15:52:19 +0200")

Hello,

Julien Lepiller <julien@lepiller.eu> skribis:

> Le Tue, 23 Apr 2019 15:33:32 +0200,
> Ludovic Courtès <ludo@gnu.org> a écrit :

[...]

>> What happens in your case is that there is no “Packaging Guidelines”
>> node—instead, it’s called “Guías de empaquetamiento” or “打包指导”.
>> Thus, Texinfo fails to build the translated manual.
>
> No, we have a small script that takes care of this. As long as the node
> name is translated somewhere near the beginning of the file, it is also
> automatically translated in the rest of the file. So that shouldn't
> cause an issue. Maybe there's an error in the script?

Oops indeed, I had misunderstood what was going on.

I applied the Spanish translation and everything went fine.

Then I looked more closely at the Simplified Chinese translation, and I
found a couple of minor issues that I modified locally for the sake of
being able to bootstrap things:

  https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3068509ac12df6f2fc6e500019a4d8bbf75d32a2

Meiyo, could you take these changes in the official PO file?

Anyway, after ‘guix pull’, “info guix.zh_CN” should also work.  :-)

Thank you, and sorry for the confusion, Julien!

Ludo’.

  parent reply	other threads:[~2019-04-23 23:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 13:33 Translation of the Guix manual & node names Ludovic Courtès
2019-04-23 13:52 ` Julien Lepiller
2019-04-23 21:48   ` Miguel
2019-04-23 21:56     ` Laura Lazzati
2019-04-26 11:01       ` Miguel
2019-04-23 21:59     ` Julien Lepiller
2019-04-23 22:45   ` Ludovic Courtès [this message]
2019-04-24  7:08   ` Meiyo Peng
2019-04-24  7:24     ` Julien Lepiller
2019-05-14  2:29       ` Meiyo Peng
2019-05-17 22:48         ` bug#35786: Some manual @ref @xref @pxref fail when untranslated pelzflorian (Florian Pelz)
2019-05-18  7:40           ` Julien Lepiller
2019-05-23  4:05           ` bug#35786: " Meiyo Peng
2022-06-11 11:24           ` bug#35786: " pelzflorian (Florian Pelz)
2019-04-23 18:11 ` Translation of the Guix manual & node names Meiyo Peng
2019-04-24  6:44   ` pelzflorian (Florian Pelz)
2019-04-24  7:31     ` Julien Lepiller
2019-04-24  8:51       ` pelzflorian (Florian Pelz)
2019-04-24  9:24         ` Julien Lepiller
2019-04-24 10:36           ` pelzflorian (Florian Pelz)
2019-04-25  8:56         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0lce3xa.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.