unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	Damien Cassou <damien@cassou.me>, Juri Linkov <juri@linkov.net>,
	Noam Postavsky <npostavs@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Lack of tooling slowing down contributions
Date: Mon, 17 Jun 2019 17:22:20 +0700	[thread overview]
Message-ID: <CAP_d_8V=p2N4ehPuFP1qfBbpYfkr-tuekKMgkxa4Dc6AHO-drw@mail.gmail.com> (raw)
In-Reply-To: <87muig35dj.fsf@mbork.pl>

On Mon, Jun 17, 2019 at 4:56 PM Marcin Borkowski <mbork@mbork.pl> wrote:

> TeX uses a nice approximate solution where a period after a capital
> letter does not mean a sentence ending.  This does not solve everything
> (of course), but helps in cases like "P. G. Wodehouse" (I love his
> Bertram Wooster stories, btw).  On the other hand, it can be tripped by
> things like "He used to work in NASA.  Now he's a full-time comic strip
> author".

I have a hypothesis that in all cases where U+002E FULL STOP is used
in a role other than sentence ending punctuation, it should either not
be followed by any spaces (as in decimals such as 3.14 or object
member access like rect.width), or be followed by a U+00A0 NO-BREAK
SPACE rather than any number of ordinary U+0020 SPACEs (as in
contractions and initials such as e.~g., Dr.~Pepper, or
P.~G.~Wodehouse). So any false positive of the simple rule “Every
U+002E U+0020 is a sentence end” is a typographical mistake to be
fixed, rather than a legitimate exception to be worked around. Any
counterexamples?

On the other hand, I have another hypothesis that this convention
would be much harder to enforce than the double-spacing one.



  reply	other threads:[~2019-06-17 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  7:38 Lack of tooling slowing down contributions Damien Cassou
2019-06-14  7:58 ` Eli Zaretskii
2019-06-14 11:19 ` Noam Postavsky
2019-06-16 19:20   ` Juri Linkov
2019-06-16 22:44     ` Stefan Monnier
2019-06-17 21:08       ` Juri Linkov
2019-06-16 23:06     ` Phil Sainty
2019-06-17  5:44       ` Van L
2019-06-17  9:53       ` Marcin Borkowski
2019-06-17 10:22         ` Yuri Khan [this message]
2019-06-17 21:19       ` Juri Linkov
2019-06-18 21:29         ` Juri Linkov
2019-06-19 12:50           ` Andy Moreton
2019-06-19 20:47             ` Juri Linkov
2019-06-19 21:26               ` Noam Postavsky
2019-06-17  6:57     ` Damien Cassou

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='CAP_d_8V=p2N4ehPuFP1qfBbpYfkr-tuekKMgkxa4Dc6AHO-drw@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=damien@cassou.me \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=mbork@mbork.pl \
    --cc=npostavs@gmail.com \
    --cc=psainty@orcon.net.nz \
    /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).