From: Al Viro <viro@ZenIV.linux.org.uk>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>,
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 04:09:58 +0100 [thread overview]
Message-ID: <20080414030958.GT9785@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080413190916.57cede66.randy.dunlap@oracle.com>
On Sun, Apr 13, 2008 at 07:09:16PM -0700, Randy Dunlap wrote:
> 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).
In a sense... Basically, the real rules are
* inter-sentence space is naturally wider than inter-word one
* if you need to stretch line, inter-sentence spaces get
proportionally more than inter-word ones.
* if you need to shrink line, they get proportionally less.
* there are fun extra considerations for quoted sentences and
friends.
For monospace almost nothing of that can be applied, but the first part
(wider inter-sentence spaces) is more painful to ignore. The ratio for
normally typeset text is going to be less than 2, but it's easier on
eyes to approximate it with 2 than with 1...
next prev parent reply other threads:[~2008-04-14 3:10 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
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 [this message]
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=20080414030958.GT9785@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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