From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Rafael Fontenelle <rafaelff@gnome.org>
Cc: help-guix@gnu.org
Subject: Re: Translating texinfo commands in Guix manual (was: Re: How to build only Guix Manual)
Date: Thu, 17 Oct 2019 09:33:40 +0200 [thread overview]
Message-ID: <20191017073340.3pj7wmk3hng62ohr@pelzflorian.localdomain> (raw)
In-Reply-To: <CAFPa+SmtFDC2V=_E7YFSwx1KicijHU++eAVS1k1GOTBxxPKQBQ@mail.gmail.com>
Thank you for your localization efforts!
On Thu, Oct 17, 2019 at 03:18:58AM -0300, Rafael Fontenelle wrote:
> For example, for Brazilian Portuguese, I have translated to:
>
> #. type: Plain text
> #: doc/guix.texi:7
> msgid "@documentencoding UTF-8"
> msgstr ""
> "@documentencoding UTF-8\n"
> "@documentlanguage pt_BR"
>
You may want to add frenchspacing:
#. type: Plain text
#: doc/guix.texi:7
msgid "@documentencoding UTF-8"
msgstr ""
"@documentencoding UTF-8\n"
"@documentlanguage pt_BR\n"
"@frenchspacing on"
I do not know if french spacing is common in Portuguese.
> Now, using @pxref, @xref and any other related texinfo command are
> translated to the target language in the resulting Guix manual.
>
> [1] https://translationproject.org/domain/texinfo_document.html
>
I always use “see @ref{…}” because @xref and @pxref are only
translated in HTML output for me, but not when running “info guix.de”.
The info command looks more right and HTML looks the same.
Regards,
Florian
next prev parent reply other threads:[~2019-10-17 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 19:41 How to build only Guix Manual Rafael Fontenelle
2019-09-02 19:57 ` Julien Lepiller
2019-09-03 0:37 ` Rafael Fontenelle
2019-09-03 8:16 ` Julien Lepiller
2019-09-03 11:08 ` Rafael Fontenelle
2019-09-03 11:33 ` Julien Lepiller
2019-09-03 12:03 ` Rafael Fontenelle
2019-10-17 6:18 ` Translating texinfo commands in Guix manual (was: Re: How to build only Guix Manual) Rafael Fontenelle
2019-10-17 7:33 ` pelzflorian (Florian Pelz) [this message]
2019-10-17 8:17 ` Rafael Fontenelle
2019-10-17 8:44 ` pelzflorian (Florian Pelz)
2019-09-03 9:22 ` How to build only Guix Manual 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=20191017073340.3pj7wmk3hng62ohr@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=help-guix@gnu.org \
--cc=rafaelff@gnome.org \
/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.
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).