From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Translation of the Guix manual & node names
Date: Thu, 25 Apr 2019 10:56:41 +0200 [thread overview]
Message-ID: <87mukeqx86.fsf@gnu.org> (raw)
In-Reply-To: <20190424085155.j2cnitew7qips2tn@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Wed, 24 Apr 2019 10:51:55 +0200")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> On Wed, Apr 24, 2019 at 09:31:59AM +0200, Julien Lepiller wrote:
>> #. type: Plain text
>> #: doc/guix.texi:7
>> msgid "@documentencoding UTF-8"
>> msgstr ""
>> "@documentencoding UTF-8\n"
>> "@documentlanguage fr\n"
>> "@frenchspacing on"
>>
> I already use this. The French manual is affected too. When you do
> `info guix.fr` or use emacs to open the manual, do you see French
> “voir: Quelque section” or English “note: Quelque section”?
My understanding is that the Info format expects a literal “Note:”
regardless of the language. It wasn’t designed with i18n in mind I
guess.
Ludo’.
prev parent reply other threads:[~2019-04-25 9:02 UTC|newest]
Thread overview: 20+ 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
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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mukeqx86.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).