From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Meiyo Peng <meiyo@riseup.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Translation of the Guix manual & node names
Date: Wed, 24 Apr 2019 08:44:14 +0200 [thread overview]
Message-ID: <20190424064414.lkxwb4k7fhm7cfb4@pelzflorian.localdomain> (raw)
In-Reply-To: <87imv4vbg4.fsf@riseup.net>
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.
Regards,
Florian
next prev parent reply other threads:[~2019-04-24 6:45 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
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) [this message]
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=20190424064414.lkxwb4k7fhm7cfb4@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=meiyo@riseup.net \
/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.