The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: Chris Torek <torek@elf.torek.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Sat, 7 Nov 2020 09:54:22 +1100	[thread overview]
Message-ID: <20201106225422.GD99027@eureka.lemis.com> (raw)
In-Reply-To: <202011061546.0A6Fkv3D034443@elf.torek.net>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On Friday,  6 November 2020 at  7:46:57 -0800, Chris Torek wrote:
>> I use single spaces between sentences, but my ancestors
>> used 2... who knows why? :).
>
> Typewriters.
>
> In typesetting, especially when doing right-margin justification,
> we have "stretchy spaces" between words.  The space after end-of-
> sentence punctuation marks is supposed to be about 50% larger than
> the width of the between-words spaces, and if the word spaces get
> stretched, so should the end-of-sentence space.

FWIW, this is the US convention.  Other countries have different
conventions.  My Ausinfo style manual states

  There is no need to increase the amount of punctuation ... at the
  end of a sentence.

I believe that this also holds for Germany.  I'm not sure that the UK
didn't have different rules again.

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

  reply	other threads:[~2020-11-06 23:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 22:10 Tyler Adams
2020-11-06  0:39 ` Kevin Bowling
2020-11-06  1:41 ` Larry McVoy
2020-11-06  5:04   ` John Cowan
2020-11-06  5:16     ` Steve Nickolas
2020-11-06  6:34     ` Rob Pike
2020-11-06 13:20       ` Will Senn
2020-11-06 15:07         ` Clem Cole
2020-11-06 15:40           ` Will Senn
2020-11-06 15:46             ` Chris Torek
2020-11-06 22:54               ` Greg 'groggy' Lehey [this message]
2020-11-06 23:29                 ` Steffen Nurpmeso
2020-11-06 22:31           ` Dave Horsfall
2020-11-06 23:41             ` Warren Toomey
2020-11-06  6:37     ` Greg 'groggy' Lehey
2020-11-06 15:06       ` Larry McVoy
2020-11-06 15:18         ` Bakul Shah
2020-11-06 15:19         ` Chris Torek
2020-11-06 16:46           ` Stephen Clark
2020-11-06 18:51         ` Jon Steinhart
2020-11-06 22:09           ` John Cowan
2020-11-06 22:44             ` Jon Steinhart
2020-11-06 22:12         ` Andy Kosela
2020-11-06 22:23           ` Larry McVoy
2020-11-07  0:16             ` Dave Horsfall
2020-11-08 23:23               ` George Michaelson
2020-11-06 17:05       ` Paul Winalski
2020-11-06 17:07         ` Larry McVoy
2020-11-06 17:25           ` Warner Losh
2020-11-06 17:13       ` Adam Thornton
2020-11-06 17:26         ` Stephen Clark
2020-11-06 18:24           ` John Cowan
2020-11-06 21:10   ` Dave Horsfall

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=20201106225422.GD99027@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=torek@elf.torek.net \
    --cc=tuhs@minnie.tuhs.org \
    /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;
as well as URLs for NNTP newsgroup(s).