unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Translation of the Guix manual & node names
Date: Wed, 24 Apr 2019 09:31:59 +0200	[thread overview]
Message-ID: <20190424093159.72666070@sybil.lepiller.eu> (raw)
In-Reply-To: <20190424064414.lkxwb4k7fhm7cfb4@pelzflorian.localdomain>

Le Wed, 24 Apr 2019 08:44:14 +0200,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :

> On Wed, Apr 24, 2019 at 02:11:23AM +0800, Meiyo Peng wrote:
> > I will improve the manual gradually.  As I said before, I have no
> > experience with i18n.  I only learned the usage of @ref, @xref and
> > @pxref until yesterday.  And there are still many new things to
> > learn. 
> 
> I wonder what is correct.  @xref is for “*Note Some section”, @pxref
> is for “*note: Some section“ and @ref is for … “*note: Some section”
> as well?  I started to translate all @xref and @pxref with @ref but it
> still produces the English word “note” in the Info reader.

That's probably because the language is still declared as English. As
soon as you declare the language as something else, these generated
texts should be OK too. If you look at the French po, you will find
this:

#. type: Plain text
#: doc/guix.texi:7
msgid "@documentencoding UTF-8"
msgstr ""
"@documentencoding UTF-8\n"
"@documentlanguage fr\n"
"@frenchspacing on"

@documentlanguage … is what you want to add. @frenchspacing is for
displaying only one space between sentences in generated files which is
the correct way to do it in French.

Maybe we could automate that a bit?

> 
> Regards,
> Florian
> 

  reply	other threads:[~2019-04-24  7:32 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 [this message]
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

  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=20190424093159.72666070@sybil.lepiller.eu \
    --to=julien@lepiller.eu \
    --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).