linux-kernel - Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080414030958.GT9785@ZenIV.linux.org.uk>
Date:	Mon, 14 Apr 2008 04:09:58 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>,
	akpm@...ux-foundation.org, corbet@....net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt

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...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/