unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nikolai Weibull <now@disu.se>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Nikolai Weibull <now@disu.se>,
	Shakthi Kannan <shakthimaan@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Spaces after periods (was: Documenting NEWS features for 25.1)
Date: Tue, 29 Dec 2015 22:05:24 +0100	[thread overview]
Message-ID: <CADdV=Ms7YNGHCgeChVSHjrABpszwZ_LJkP3SqTrjf3v6=bXETg@mail.gmail.com> (raw)
In-Reply-To: <87r3i5848k.fsf@mbork.pl>

On Tue, Dec 29, 2015 at 8:05 PM, Marcin Borkowski <mbork@mbork.pl> wrote:

> On 2015-12-29, at 18:32, Nikolai Weibull <now@disu.se> wrote:

>> I haven’t seen a style guide that says anything other than that one
>> space is preferred.  However, I thought the general rule was to use
>> two spaces to make it easy for software (oh, the continued irony of it
>> all) to distinguish sentence-ending periods from other periods.

> Don't really see the irony: this is just plain difficult for a machine.
> (I also use two spaces, btw.)

It was a reference to the thread regarding apostrophe choices, where
the fact that the Unicode Consortium chose U+2019 as the apostrophe
character for similar reasons. was discussed  Just because something’s
difficult doesn’t mean we shouldn’t try to push it towards the
computer’s set of responsibilities.  Natural language processing is of
course an exceedingly difficult problem to solve, so I, as you,
continue to use two spaces.

>> Also, any typesetting software that doesn’t fold multiple spaces into
>> one isn’t a typesetting software.  Microsoft Word isn’t a typesetting
>> software.  TeX is a typesetting software, so using multiple spaces
>> shouldn’t affect the output at all.  (Perhaps Texinfo is different?)
>> Though, TeX, as far as I recall, favors adding space after a period
>> when justifying a paragraph.

> To be more precise, it does it by default, but it can be turned off (by
> \frenchspacing).  Also, in TeX, not only are the spaces after periods
> larger, but they also grow "faster" when justifying text (as you said).
> See "space factor" in The TeXbook, if you are curious about the
> details.  (Interestingly enough, this mechanism can be hackedto achieve
> some other goals, too.)

> OTOH, Bringhurst criticizes the above style very harshly.

Yes, Bringhurst is very particular in many questions relating to typesetting.

> OYAH, https://xkcd.com/1285/ . ;-)

:-)



  reply	other threads:[~2015-12-29 21:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151212115202.16784.72345@vcs.savannah.gnu.org>
     [not found] ` <E1a7iiY-0004NK-Ky@vcs.savannah.gnu.org>
2015-12-15  1:36   ` [Emacs-diffs] emacs-25 3e14bad: Document new features of Prettify Mode John Wiegley
2015-12-15  3:39     ` Eli Zaretskii
2015-12-15  6:10       ` John Wiegley
2015-12-15 17:51         ` Shakthi Kannan
2015-12-15 17:58           ` Documenting NEWS features for 25.1 (was: [Emacs-diffs] emacs-25 3e14bad: Document new features of Prettify Mode) John Wiegley
2015-12-15 18:34             ` Eli Zaretskii
2015-12-16  6:09               ` Shakthi Kannan
2015-12-16  6:44                 ` Documenting NEWS features for 25.1 John Wiegley
2015-12-16  7:59                   ` Shakthi Kannan
2015-12-16 10:20                     ` Eli Zaretskii
2015-12-16 10:36                       ` Shakthi Kannan
2015-12-16 11:11                         ` Eli Zaretskii
2015-12-16 12:29                           ` Shakthi Kannan
2015-12-21 17:09                             ` Shakthi Kannan
2015-12-21 17:28                               ` Eli Zaretskii
2015-12-24 16:49                                 ` Shakthi Kannan
2015-12-25 14:24                                   ` Eli Zaretskii
2015-12-28 17:25                                     ` Shakthi Kannan
2015-12-29 16:59                                       ` Eli Zaretskii
2015-12-29 17:05                                         ` Spaces after periods (was: Documenting NEWS features for 25.1) John Wiegley
2015-12-29 17:30                                           ` Spaces after periods David Kastrup
2015-12-29 17:32                                           ` Spaces after periods (was: Documenting NEWS features for 25.1) Nikolai Weibull
2015-12-29 17:58                                             ` Ingo Lohmar
2015-12-29 19:05                                             ` Marcin Borkowski
2015-12-29 21:05                                               ` Nikolai Weibull [this message]
2015-12-30  7:46                                             ` Spaces after periods Random832
2015-12-30  7:59                                               ` Nikolai Weibull
2015-12-29 18:15                                           ` Spaces after periods (was: Documenting NEWS features for 25.1) Eli Zaretskii
2015-12-29 19:56                                             ` Spaces after periods John Wiegley
2015-12-30  5:40                                         ` Documenting NEWS features for 25.1 Shakthi Kannan
2015-12-30 17:49                                           ` Eli Zaretskii
2015-12-31  5:33                                             ` Shakthi Kannan

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADdV=Ms7YNGHCgeChVSHjrABpszwZ_LJkP3SqTrjf3v6=bXETg@mail.gmail.com' \
    --to=now@disu.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mbork@mbork.pl \
    --cc=shakthimaan@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).