From: karl@freefriends.org (Karl Berry)
Cc: juri@jurta.org, bob@rattlesnake.com, emacs-devel@gnu.org
Subject: Re: 3 dots vanish at end of filled line
Date: Sat, 8 Oct 2005 19:14:19 -0500 [thread overview]
Message-ID: <200510090014.j990EJb27028@f7.net> (raw)
In-Reply-To: <E1EONco-0000yD-St@fencepost.gnu.org>
There should not be
whitespace before an ellipsis in English text.
I must beg to differ. Virtually every book I've seen has space before
(most) ellipses.
Aside from typographical matters, ellipses seem to most often be used to
stand for a word rather than as "trailing" punctuation. Here are a few
random samples from the Texinfo manual:
Permission is granted to @dots{}
...
one (not Info, not @TeX{}, @dots{}).
...
@item @@iftex @dots{} @@end iftex
...
than `It is recommended that @dots{}''.
It seems wrong to me to omit such spaces.
There are over 130 occurrences of spaces before @dots in the Texinfo
manuals (I didn't search others). At a glance, the spaces seem
desirable and even necessary to me. I think a blanket warning would be
a bad mistake, and I don't see any way to distinguish the problematic
cases.
Certainly there are times when no space should be there; so then the
author should leave out the space in the input. Or no line break; then
the author should use a tie.
karl
next prev parent reply other threads:[~2005-10-09 0:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:32 3 dots vanish at end of filled line Karl Berry
2005-10-07 21:12 ` Juri Linkov
2005-10-07 21:21 ` Karl Berry
2005-10-07 21:47 ` Juri Linkov
2005-10-07 23:12 ` Karl Berry
2005-10-07 23:56 ` Luc Teirlinck
2005-10-08 2:54 ` Luc Teirlinck
2005-10-08 22:57 ` Richard M. Stallman
2005-10-09 0:14 ` Karl Berry [this message]
2005-10-09 0:57 ` Luc Teirlinck
2005-10-09 6:11 ` Juri Linkov
2005-10-09 17:17 ` Karl Berry
2005-10-09 19:16 ` Luc Teirlinck
2005-10-10 15:00 ` Stefan Monnier
2005-10-10 17:07 ` Karl Berry
2005-10-10 18:01 ` Stefan Monnier
2005-10-11 14:46 ` Richard M. Stallman
2005-10-11 17:06 ` Stefan Monnier
2005-10-10 23:48 ` Richard M. Stallman
2005-10-10 23:48 ` Richard M. Stallman
2005-10-11 2:18 ` Luc Teirlinck
2005-10-11 3:31 ` Luc Teirlinck
2005-10-11 22:42 ` Richard M. Stallman
2005-10-12 0:21 ` Luc Teirlinck
2005-10-12 19:47 ` Stefan Monnier
2005-10-13 20:10 ` Richard M. Stallman
2005-10-28 4:41 ` KOBAYASHI Yasuhiro
2005-10-10 6:18 ` Juri Linkov
2005-10-09 19:54 ` Luc Teirlinck
2005-10-10 4:14 ` Richard M. Stallman
2005-10-10 15:02 ` Stefan Monnier
2005-10-10 23:47 ` Richard M. Stallman
2005-10-09 11:09 ` Robert J. Chassell
2005-10-10 4:14 ` Richard M. Stallman
2005-10-10 12:21 ` Robert J. Chassell
2005-10-10 23:47 ` Richard M. Stallman
2005-10-11 12:57 ` Robert J. Chassell
2005-10-20 11:11 ` Juri Linkov
2005-10-20 23:38 ` Richard M. Stallman
2005-10-21 11:55 ` Juri Linkov
2005-10-21 22:19 ` Richard M. Stallman
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=200510090014.j990EJb27028@f7.net \
--to=karl@freefriends.org \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.