Computer Old Farts Forum
 help / color / mirror / Atom feed
From: cym224 at gmail.com (Nemo Nusquam)
Subject: [COFF] [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 21:52:57 -0500	[thread overview]
Message-ID: <4cb3465d-ed2f-104b-494f-4fd8c97f595b@gmail.com> (raw)
In-Reply-To: <CAC20D2ORm6S0ZpW8BnKX8dW+uxxp-fC3+t1e=uWDdNNeoWRiQw@mail.gmail.com>

On 11/06/20 11:22, Clem Cole wrote:
> Exactly -- just re-read Will's question.  2 spaces after punctuation 
> is a fix-size typeface solution to the 1.5 typographer layout.
Is it not an m-space after a full-stop?  (Though Brinhurst eschewed this 
in the fourth edition.)

> I was referring to why typed papers were traditionally double spaced 
> between the lines.
I was advised to this with drafts for copy-editing but legal documents 
are always double-spaced lines (and I know not why).

N.

> On Fri, Nov 6, 2020 at 11:02 AM Chris Torek <torek at elf.torek.net 
> <mailto:torek at elf.torek.net>> 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.  Note that this is
>     all in the variable-pitch font world.
>
>     Since typewriters are fixed-pitch, the way to emulate the
>     1.5-space-wide gap is to expand it to 2.
>
>     Chris
>



  parent reply	other threads:[~2020-11-07  2:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEuQd1AWs=jpHYk3nGpKsBV=qF4DZVXvXzynSeDK5S-r-hfryw@mail.gmail.com>
     [not found] ` <20201106014109.GP26296@mcvoy.com>
     [not found]   ` <CAD2gp_Q-wTvG2cAW5goJFYW3A6qF9zOuTh=Y4Kahh0nLBtof2Q@mail.gmail.com>
     [not found]     ` <20201106063725.GB99027@eureka.lemis.com>
     [not found]       ` <5BE1CBD5-C9EB-45D4-B135-E58BCCCBE38C@gmail.com>
     [not found]         ` <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net>
2020-11-06 17:56           ` clemc
     [not found]       ` <20201106150609.GR26296@mcvoy.com>
     [not found]         ` <202011061519.0A6FJOAx034308@elf.torek.net>
2020-11-06 23:08           ` grog
     [not found]         ` <CALMnNGg=9KHCwqaqdFESBQr=Ru_qzM=x-S2fc=ewgJNf2zLRFQ@mail.gmail.com>
     [not found]           ` <20201106222302.GG26411@mcvoy.com>
2020-11-07  0:16             ` dave
     [not found]     ` <CAKzdPgx1Ptu=sahO3o5KYS-A=vnfXK-hs=QeVwO_Vd1cFfaeqw@mail.gmail.com>
     [not found]       ` <a588c934-e403-2a4e-4701-669b8c14e989@gmail.com>
     [not found]         ` <CAC20D2PPw3Ua3-VpMYjh=NaC09=9Q528kqEvE7SvmO3Ly2JO0A@mail.gmail.com>
     [not found]           ` <175409f6-af94-601e-3db3-a5af5d7f64d0@gmail.com>
2020-11-06 15:53             ` clemc
2020-11-06 19:22               ` tytso
2020-11-06 19:24                 ` clemc
2020-11-06 22:58               ` grog
2020-11-07 21:04                 ` clemc
2020-11-07 23:05                   ` dave
2020-11-09  4:36                   ` [COFF] Daisy wheel printers (was: [TUHS] The Elements Of Style: UNIX As Literature) grog
2020-11-09 14:26                     ` clemc
2020-11-10  0:10                       ` grog
2020-11-10 14:48                         ` clemc
2020-11-10 15:10                           ` stewart
2020-11-09 22:08                     ` dave
2020-11-10  0:48                       ` grog
     [not found]             ` <202011061546.0A6Fkv3D034443@elf.torek.net>
2020-11-06 16:22               ` [COFF] [TUHS] The Elements Of Style: UNIX As Literature clemc
2020-11-06 18:12                 ` torek
2020-11-07  2:52                 ` cym224 [this message]
     [not found]               ` <20201106225422.GD99027@eureka.lemis.com>
     [not found]                 ` <20201106232901.AkY2I%steffen@sdaoden.eu>
2020-11-07  4:22                   ` grog
2020-11-07 20:31                     ` steffen
2020-11-11  8:31           ` [COFF] " peter
2020-11-11 12:21             ` tih
2020-11-11 21:09             ` dave

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=4cb3465d-ed2f-104b-494f-4fd8c97f595b@gmail.com \
    --to=coff@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).