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 10:44:40 +0200 [thread overview]
Message-ID: <20191017084440.6xmbskjcmb5eufkn@pelzflorian.localdomain> (raw)
In-Reply-To: <CAFPa+SmraUgvpTb0Kin-O0YrtHx0gW8_idbk09jkVfan8_wN_w@mail.gmail.com>
On Thu, Oct 17, 2019 at 05:17:43AM -0300, Rafael Fontenelle wrote:
> It seems the French Spacing consists in a space between last word in a
> sentence and ending punctuation, and only one space between sentences.
> If I've got it right, then it doesn't apply to Portuguese. We normally
> use no space between last word and ending punctuation, and also only
> one space between sentences.
>
I believe the Texinfo command @frenchspacing only affects whether
there is a single or double space after a sentence. What you describe
sounds like you would want to use French spacing (although it is
apparently without effect in HTML output).
See the Texinfo manual (“info texinfo”), section
12.3.4 '@frenchspacing' VAL: Control Sentence Spacing.
I believe whether you put a space before … or quotes is *not* affected by
Texinfo’s @frenchspacing command, despite the real meaning of French spacing:
#: gnu/installer/newt/network.scm:125
msgid "Waiting for Internet access establishment..."
msgstr "Auf Herstellung des Internetzugangs wird gewartet …"
> Thanks for the suggestion, though.
>
> > 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.
>
> Testing the info output, it shows " *note <link>:: " (where <link> is
> the target link. Is this the same you see in not using “see @ref{…}” ?
>
> Regards,
> Rafael Fontenelle
This is hard to explain. Both are wrong. The proper solution might
be to fix Texinfo and use @pxref and @xref where appropriate, or
alternatively to get rid of useless @pxref and @xref. For now though,
I see:
With @pxref, in HTML, “veja <link>” (translated), in `info' “*note <link>“.
With “see @ref”, in HTML, “veja <link>”, in `info' “veja *note <link>”.
Therefore I think “veja @ref” is less wrong. I guess we should ask on
the Texinfo mailing list upstream.
Regards,
Florian
next prev parent reply other threads:[~2019-10-17 8:44 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)
2019-10-17 8:17 ` Rafael Fontenelle
2019-10-17 8:44 ` pelzflorian (Florian Pelz) [this message]
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=20191017084440.6xmbskjcmb5eufkn@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).