Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Improving the spam.el documentation.
Date: Tue, 08 Jun 2004 13:28:24 +1000	[thread overview]
Message-ID: <87n03esp7r.fsf@enki.rimspace.net> (raw)
In-Reply-To: <m31xkq7pm3.fsf@defun.localdomain>

On 8 Jun 2004, Jesper Harder wrote:
> 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.

Ah, dang. I really /should/ have dug out my typography book and checked,
rather than relying on half-remembered information. I feel silly now.

[...]

> 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.

Ah. Must beat `texinfo-mode' to reset the relevant variable, then.
    Daniel
-- 
It is always possible to aglutenate multiple separate problems into a single
complex interdependent solution. In most cases this is a bad idea.
        -- RFC 1925




      reply	other threads:[~2004-06-08  3:28 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
2004-06-08  3:28           ` Daniel Pittman [this message]

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=87n03esp7r.fsf@enki.rimspace.net \
    --to=daniel@rimspace.net \
    /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).