From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nikolai Weibull Newsgroups: gmane.emacs.devel Subject: Re: Spaces after periods (was: Documenting NEWS features for 25.1) Date: Tue, 29 Dec 2015 22:05:24 +0100 Message-ID: References: <20151212115202.16784.72345@vcs.savannah.gnu.org> <83poy82xe0.fsf@gnu.org> <834mfj36ij.fsf@gnu.org> <83vb7y1yqg.fsf@gnu.org> <83oadq1wdq.fsf@gnu.org> <8360zrsoct.fsf@gnu.org> <83poxuli6m.fsf@gnu.org> <83h9j1dwcu.fsf@gnu.org> <87r3i5848k.fsf@mbork.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1451423148 17429 80.91.229.3 (29 Dec 2015 21:05:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2015 21:05:48 +0000 (UTC) Cc: Nikolai Weibull , Shakthi Kannan , Eli Zaretskii , Emacs Developers To: Marcin Borkowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 29 22:05:38 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aE1Sc-0006Xl-64 for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2015 22:05:38 +0100 Original-Received: from localhost ([::1]:50155 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aE1Sb-00081A-Ek for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2015 16:05:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57039) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aE1SX-000815-Gc for emacs-devel@gnu.org; Tue, 29 Dec 2015 16:05:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aE1SW-0005jl-DI for emacs-devel@gnu.org; Tue, 29 Dec 2015 16:05:33 -0500 Original-Received: from disu.se ([71.19.156.204]:47318) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aE1SR-0005iO-CQ; Tue, 29 Dec 2015 16:05:27 -0500 Original-Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by disu.se (Postfix) with ESMTPSA id BFFC9C03A; Tue, 29 Dec 2015 22:05:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disu.se; s=mail; t=1451423126; bh=MF1Fsh2ifPMgEu1UUNRrmc2KR3Mr38cgRsswvhnFohg=; h=In-Reply-To:References:Date:Subject:From:To:Cc:From; b=uesUqbJBegjUo5N4PqzquoM/z3BuTu6R6wtoPM6tg8DGDOfViNjNiCmnflD7XBlZ9 LNDg/t04wQuRWIZkJ8bVcyUbU6s3/xSg2qxrYIegohDMTJ8VZsktGCSSc3hmJFRlfN l6OCPpbXDgACZwIgCDxncmJtrmB9UUGrk+VvuIOQ= Original-Received: by mail-lb0-f171.google.com with SMTP id bc4so108150279lbc.2; Tue, 29 Dec 2015 13:05:25 -0800 (PST) X-Received: by 10.112.126.164 with SMTP id mz4mr13052281lbb.70.1451423124074; Tue, 29 Dec 2015 13:05:24 -0800 (PST) Original-Received: by 10.25.64.7 with HTTP; Tue, 29 Dec 2015 13:05:24 -0800 (PST) In-Reply-To: <87r3i5848k.fsf@mbork.pl> X-Gmail-Original-Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 71.19.156.204 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197142 Archived-At: On Tue, Dec 29, 2015 at 8:05 PM, Marcin Borkowski wrote: > On 2015-12-29, at 18:32, Nikolai Weibull wrote: >> I haven=E2=80=99t 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=E2=80= =99s difficult doesn=E2=80=99t mean we shouldn=E2=80=99t try to push it towards = the computer=E2=80=99s 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=E2=80=99t fold multiple spaces= into >> one isn=E2=80=99t a typesetting software. Microsoft Word isn=E2=80=99t = a typesetting >> software. TeX is a typesetting software, so using multiple spaces >> shouldn=E2=80=99t affect the output at all. (Perhaps Texinfo is differe= nt?) >> 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 typesettin= g. > OYAH, https://xkcd.com/1285/ . ;-) :-)