From: karl@freefriends.org (Karl Berry)
To: dsmich@roadrunner.com, guile-devel@gnu.org
Subject: Re: two spaces after sentence + other doc janitorial duties
Date: Mon, 12 Jul 2010 00:51:04 GMT [thread overview]
Message-ID: <201007120051.o6C0p4nE015502@f7.net> (raw)
[Sorry if there has been later replies on this.]
> >> Why is this the case? TeX itself gets this right, why can't makeinfo?
There is no overwhelming reason, it's just the historical fact that it's
never tinkered with intersentence spaces, aside from trying
half-heartedly to detect sentences at the end of lines.
rms wrote all this stuff originally, and in his world, the source files
all have two spaces at the end of sentences already, for the sake of
Emacs sentence commands. So there was no reason for him to have
texinfo-format-buffer (or later makeinfo) to do anything.
Perhaps one day it will, it's on the wishlist, but don't hold your
breath. Sorry.
karl
next reply other threads:[~2010-07-12 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 0:51 Karl Berry [this message]
2010-07-13 21:13 ` two spaces after sentence + other doc janitorial duties Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2010-06-25 16:35 Thien-Thi Nguyen
2010-06-28 13:57 ` Andy Wingo
2010-07-02 13:23 ` Ludovic Courtès
2010-07-08 10:10 ` Andy Wingo
2010-07-08 17:04 ` dsmich
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201007120051.o6C0p4nE015502@f7.net \
--to=karl@freefriends.org \
--cc=dsmich@roadrunner.com \
--cc=guile-devel@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).