Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Improving the spam.el documentation.
Date: Tue, 08 Jun 2004 04:25:24 +0200	[thread overview]
Message-ID: <m31xkq7pm3.fsf@defun.localdomain> (raw)
In-Reply-To: <87aczeu8v3.fsf@enki.rimspace.net> (Daniel Pittman's message of "Tue, 08 Jun 2004 11:38:40 +1000")

Daniel Pittman <daniel@rimspace.net> writes:

> On 8 Jun 2004, Ted Zlatanov wrote:

Ted, your message is missing on news.gnus.org.

>> I thought there were always two spaces after a period.  Is Texinfo
>> different?
>
> Nope. "French" spacing is two space after a period, and that is one
> of the two major styles. The other is, of course, a single space
> after a period.

It's the other way around (at least in the Tex(info) world).
\frenchspacing suppresses extra end-of-sentence space whereas
\nonfrenchspacing (the default) puts extra space after punctuation in
typeset output.

> Er, it may be that texinfo, or the documentation, has a standard
> that I didn't spot, or that was changed when I hit M-q to reformat a
> paragraph; my Emacs is set to single-space after sentence mode.

The standard in Texinfo is to use two spaces after a period:

  enter a period as you would if you were using a typewriter, which
  means you put two spaces after the period, question mark, or
  exclamation mark that ends a sentence.

-- 
Jesper Harder                                <http://purl.org/harder/>



  reply	other threads:[~2004-06-08  2:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 13:26 Daniel Pittman
2004-05-28 15:00 ` Jesper Harder
2004-05-28 16:27 ` Ted Zlatanov
2004-05-31 13:34   ` Daniel Pittman
2004-06-07 16:56     ` Ted Zlatanov
2004-06-08  1:29       ` Daniel Pittman
2004-06-08 14:31         ` Ted Zlatanov
2004-06-07 17:06     ` Ted Zlatanov
2004-06-08  1:38       ` Daniel Pittman
2004-06-08  2:25         ` Jesper Harder [this message]
2004-06-08  3:28           ` Daniel Pittman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m31xkq7pm3.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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 NNTP newsgroup(s).