From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
akpm@linux-foundation.org, corbet@lwn.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt
Date: Mon, 14 Apr 2008 06:33:09 +0400 [thread overview]
Message-ID: <4802C265.8060802@gmail.com> (raw)
In-Reply-To: <20080413190916.57cede66.randy.dunlap@oracle.com>
Randy Dunlap пишет:
> On Sun, 13 Apr 2008 23:45:47 +0100 Al Viro wrote:
>
>> On Mon, Apr 14, 2008 at 02:25:05AM +0400, Dmitri Vorobiev wrote:
>>
>>> Actually, I was doubting whether the "2 spaces" thing was
>>> intentional or not. The overwhelming majority of the sentences in
>>> this document use only one space after a period, however, and this
>>> made me decide that the "2 spaces" thing had not been deliberate
>>> but just a typo.
>>>
>>> Are there any rules about using spaces after a period at the end
>>> of a sentence?
>> See Knuth (TeXbook) for the story on that...
>
> I googled that but I don't see the history there.
>
> AFAIK, 2 spaces at the end of sentences is a typewriter-ism, for easier
> visual separation of sentences.
> Probably (just guessing here) has to do with monospace fonts vs.
> (not having) proportional ones there (usually).
The following Wikipedia article is the most complete and exhaustive source
I could find while researching the double spacing rules:
http://en.wikipedia.org/wiki/French_spacing
To put it briefly, there are three main conventions about inter-sentence
spacing:
o English spacing a.k.a. American typewriter spacing: two spaces after full stop;
o French spacing, i.e. one space;
o traditional typography, which uses proportional fonts and is therefore not
very much interesting here.
Offhand, it seems that the double spacing convention is being currently used
in a more or less consistent manner throughout Linux docs. It also seems to
me that this can be made a requirement and documented somewhere.
Thanks,
Dmitri
>
> ---
> ~Randy
> [Yes, I learned to type on a manual typewriter.]
>
next prev parent reply other threads:[~2008-04-14 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 18:26 [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt Dmitri Vorobiev
2008-04-13 22:10 ` Randy Dunlap
2008-04-13 22:25 ` Dmitri Vorobiev
2008-04-13 22:45 ` Al Viro
2008-04-13 22:49 ` Dmitri Vorobiev
2008-04-14 2:09 ` Randy Dunlap
2008-04-14 2:33 ` Dmitri Vorobiev [this message]
2008-04-14 13:52 ` Jonathan Corbet
2008-04-14 14:21 ` Dmitri Vorobiev
2008-04-14 15:07 ` Randy Dunlap
2008-04-14 15:13 ` Jan Engelhardt
2008-04-14 3:09 ` Al Viro
2008-04-13 23:55 ` Nick Andrew
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=4802C265.8060802@gmail.com \
--to=dmitri.vorobiev@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=viro@ZenIV.linux.org.uk \
/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