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] [day] [month] [year] [list]

Message-ID: <alpine.LNX.1.10.0804141709060.9651@fbirervta.pbzchgretzou.qr>
Date:	Mon, 14 Apr 2008 17:13:13 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>
cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Al Viro <viro@...IV.linux.org.uk>, 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 Monday 2008-04-14 04:33, Dmitri Vorobiev wrote:
>
>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;

French spacing has even weirder inter-word/operator spacing,
like « this » and that !

>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.

I object. No matter how many (unescaped) spaces you cram in after a sentence
stop, HTML engines will happily squash it when displayed [in text/html
mode of course], like <p>do as much english spacing.       as you want,
it's still correctly fixed by the display :-)</p>.

--
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/