unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: line adjustment at the end of a sentence
Date: Wed, 26 Sep 2012 21:23:44 +0200	[thread overview]
Message-ID: <831uhoh9kv.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8W=HuP90p5qCFO33mC=LHzWTLy_L6GrzrC7xRDs7JFntQ@mail.gmail.com>

> Date: Thu, 27 Sep 2012 00:44:54 +0700
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Cc: Tom Kramer <kramer@cme.nist.gov>,
> 	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> 
> Differentiating between end-of-sentence full stop and in-sentence
> period by the number of spaces is an artifact of pre-Unicode
> typography. When the only available space was the ASCII 0x20, it made
> sense. Now it doesn’t, as we have the U+0020 SPACE, the U+00A0
> NON-BREAKING SPACE, and the U+2009/U+200A THIN SPACE and HAIR SPACE,
> respectively, as well as other fixed-width spaces.

But in the real world, there's still a lot of text with 2 spaces
between sentences, and Emacs needs to DTRT with that.  An editor
cannot throw in the towel when it bumps into text that uses two
spaces.




  reply	other threads:[~2012-09-26 19:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 10:56 line adjustment at the end of a sentence T.F. Torrey
2012-09-26 12:00 ` Tom Kramer
2012-09-26 17:12   ` Ludwig, Mark
2012-09-26 17:44     ` Yuri Khan
2012-09-26 19:23       ` Eli Zaretskii [this message]
2012-09-26 17:50     ` Drew Adams
     [not found]     ` <mailman.9789.1348681498.855.help-gnu-emacs@gnu.org>
2012-09-27  0:34       ` Stefan Monnier
2012-09-27  5:26         ` Drew Adams
2012-09-27 12:19           ` Stefan Monnier
2012-09-27 14:57             ` Drew Adams
2012-09-27 16:37               ` Stefan Monnier
2012-09-27 17:00                 ` Drew Adams
     [not found]                 ` <mailman.9862.1348765244.855.help-gnu-emacs@gnu.org>
2012-09-27 18:04                   ` Stefan Monnier
     [not found] ` <mailman.9790.1348681903.855.help-gnu-emacs@gnu.org>
2012-09-26 20:35   ` Barry Margolin
2012-09-27  3:21     ` Eric Abrahamsen
2012-09-29 14:09       ` Sivaram Neelakantan
     [not found]       ` <mailman.9978.1348927764.855.help-gnu-emacs@gnu.org>
2012-09-29 17:13         ` Stefan Monnier
2012-10-14  1:21           ` David Combs
2012-10-14 15:58             ` Joe Fineman
2012-10-14 18:13               ` PJ Weisberg
     [not found]               ` <mailman.10975.1350238417.855.help-gnu-emacs@gnu.org>
2012-11-25  1:05                 ` David Combs
2012-12-02  3:03                   ` J. David Boyd
2012-10-19 22:03             ` Stefan Monnier
     [not found] <mailman.9731.1348608357.855.help-gnu-emacs@gnu.org>
2012-09-25 21:41 ` Pascal J. Bourguignon
  -- strict thread matches above, loose matches on Subject: below --
2012-09-25 21:25 Tom Kramer
2012-09-25 21:50 ` Eli Zaretskii
2012-09-25 23:28 ` Peter Dyballa
2012-09-25 12:54 Tom Kramer
2012-09-25 16:29 ` Eli Zaretskii
2012-09-25 18:40 ` Óscar Fuentes
2012-09-25 21:18 ` Pascal J. Bourguignon
2012-09-25 21:53   ` Eli Zaretskii

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=831uhoh9kv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).