unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: two spaces after sentence + other doc janitorial duties
Date: Thu, 08 Jul 2010 11:10:34 +0100	[thread overview]
Message-ID: <m3y6dms2qt.fsf@unquote.localdomain> (raw)
In-Reply-To: <87aaqauiep.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 02 Jul 2010 15:23:26 +0200")

Heya Ludovic,

On Fri 02 Jul 2010 14:23, ludo@gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>> On Fri 25 Jun 2010 18:35, Thien-Thi Nguyen <ttn@gnuvola.org> writes:
>>
>>> Normally, texinfo source should have two spaces after each sentence:
>>>
>>>    Blah the first. Blah more.      ;; only one space, not cool
>>>    Blah the first.  Blah more.     ;; two spaces, ok
>>
>> Why is this the case? TeX itself gets this right, why can't makeinfo?
>
> I’m not sure whether/how TeX gets it right.

For TeX, the end of a sentence comes when a terminal punctuation mark
(e.g., `.' or `!') is followed by any amount of whitespace, and not
preceded by a capital letter. For example the period after the T in
"I.T. Department" does not end the sentence.

You do have to play tricks with TeX when you're doing something that
doesn't conform to its expectations; see "Inserting Space" in the
texinfo manual.

But since you have to placate TeX already, for print output, it seems
the one-space or two-space shenanigans are completely redundant, and
provide no new information. Info output is already reflowed in
paragraphs, I don't see why its textual rendering doesn't follow TeX's
rules rather than introducing its own redundancies on top of it.

If it is how it must be for GNU, though, then I will try to change. But
I don't like it.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-07-08 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 16:35 two spaces after sentence + other doc janitorial duties 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 [this message]
2010-07-08 17:04       ` dsmich
  -- strict thread matches above, loose matches on Subject: below --
2010-07-12  0:51 Karl Berry
2010-07-13 21:13 ` Andy Wingo

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=m3y6dms2qt.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).