From: Alejandro Colomar <alx.manpages@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: linux-man@vger.kernel.org, Reuben Thomas <rrt@sc3d.org>,
Steffen Nurpmeso <steffen@sdaoden.eu>,
Martin Sebor <msebor@redhat.com>,
Alejandro Colomar <alx@kernel.org>
Subject: 2 spaces after the end of a sentence is the _right_ amount (was: [PATCH] iconv.3: Clarify the behavior when input is untranslatable)
Date: Sun, 21 May 2023 22:53:26 +0200 [thread overview]
Message-ID: <806c6e68-6646-e42b-0ee0-a0fec1cc0291@gmail.com> (raw)
In-Reply-To: <2906989.o0KrE1Onz3@nimes>
[-- Attachment #1.1: Type: text/plain, Size: 736 bytes --]
Hi Bruno,
On 5/21/23 21:37, Bruno Haible wrote:
> Hi Alejandro,
>
>> Please use semantic newlines. See man-pages(7):
>
> Thanks for explaining. I wondered whether I should use one space or two spaces
> after the end of a sentence,
That one's easy: one space is always wrong. :-)
<https://web.archive.org/web/20171107164742/http://www.heracliteanriver.com/?p=324>
<https://lore.kernel.org/linux-man/9c5c5744-dde0-b333-09e0-ba9d92aa96b1@gmail.com/T/#u>
<https://lists.gnu.org/archive/html/groff/2020-11/msg00076.html>
> but found no precedent for either style. This
> explains it :)
:)
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-21 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 10:31 [PATCH] iconv.3: Clarify the behavior when input is untranslatable Alejandro Colomar
2023-05-21 10:32 ` Alejandro Colomar
2023-05-21 11:11 ` Bruno Haible
2023-05-21 14:41 ` Alejandro Colomar
2023-05-21 19:37 ` Bruno Haible
2023-05-21 20:53 ` Alejandro Colomar [this message]
2023-05-21 20:57 ` Alejandro Colomar
2023-05-24 22:07 ` Bruno Haible
2023-05-24 23:25 ` Alejandro Colomar
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=806c6e68-6646-e42b-0ee0-a0fec1cc0291@gmail.com \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=bruno@clisp.org \
--cc=linux-man@vger.kernel.org \
--cc=msebor@redhat.com \
--cc=rrt@sc3d.org \
--cc=steffen@sdaoden.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox