From: Rafael Fontenelle <rafaelff@gnome.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: How to build only Guix Manual
Date: Tue, 3 Sep 2019 08:08:14 -0300 [thread overview]
Message-ID: <CAFPa+SmFmgJOTuZD9BFRV2WqwBvNT7-uu5nGQfvWBdRJKFCFGQ@mail.gmail.com> (raw)
In-Reply-To: <29D826AB-D5B7-4902-80D3-FB9EACCA5CF9@lepiller.eu>
Em ter, 3 de set de 2019 às 05:16, Julien Lepiller
<julien@lepiller.eu> escreveu:
>
> I don't understand why they are not generated when building individual info manuals. You can build these files with:
>
> make doc/os-config-bare-bones.texi
> ect
>
> Note that we don't provide a way to translate these examples yet, so you'll have to use the English filename for now, or help us get them translated :)
Thanks Julien and Ludovic (in other email) for the replies.
Yep, adding the above command did the job and the build of HTML manual
worked just fine.
Doubt: is it safe to replace @pxref and @xref with @ref? These two
macros prefix an untranslatable "see" and "See", respectively, before
the linked section. So I am considering using "veja @ref" and "Veja
@ref" (veja = "see" translation) instead.
next prev parent reply other threads:[~2019-09-03 11:08 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 [this message]
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)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFPa+SmFmgJOTuZD9BFRV2WqwBvNT7-uu5nGQfvWBdRJKFCFGQ@mail.gmail.com \
--to=rafaelff@gnome.org \
--cc=help-guix@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.