unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Schroeder <kensanata@gmail.com>
Cc: "Björn Lindström" <bkhl@member.fsf.org>,
	rcyeske@gmail.com, emacs-devel@gnu.org
Subject: Re: rcirc manual
Date: Fri, 13 Jan 2006 15:10:13 +0100	[thread overview]
Message-ID: <9abbd5730601130610w4507670aqd122cb33bc564486@mail.gmail.com> (raw)
In-Reply-To: <uek3cs78r.fsf@gnu.org>

Thanks for the feedback on the manual, Eli.

As for the em dash suggestion: Is there a convention or tradition for
the GNU manuals to prefer em dashes?  I'm reading The Elements of
Typographical Style by Robert Bringhurst, at the moment.  On p 80 he
says: "The em dash is the nineteenth-century standard, still
prescribed in many editorial style books, but the em dash is too long
for use with the best text faces.  [...] Used as a phrase marker --
thus -- the en dash is set with a normal word space either side."  I
think in European typography in general, em dashes are rarely used.

  reply	other threads:[~2006-01-13 14:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 17:47 rcirc manual Björn Lindström
2006-01-13 11:21 ` Eli Zaretskii
2006-01-13 14:10   ` Alex Schroeder [this message]
2006-01-13 15:08     ` Eli Zaretskii
2006-01-13 15:11       ` Alex Schroeder
2006-01-14 16:14     ` Richard M. Stallman
2006-01-13 15:48   ` Thien-Thi Nguyen
2006-01-13 15:55     ` Eli Zaretskii
2006-01-13 22:16       ` Robert J. Chassell
2006-01-14  8:51         ` Eli Zaretskii
2006-01-14 12:20           ` Robert J. Chassell
2006-01-14 15:10             ` Eli Zaretskii
2006-01-14 17:47               ` Robert J. Chassell
2006-01-15 23:07                 ` Richard M. Stallman
2006-01-15  7:49           ` Richard M. Stallman
2006-01-15 19:48             ` Eli Zaretskii
2006-01-15 22:23               ` Karl Berry
2006-01-16  4:26                 ` Eli Zaretskii
2006-01-15 22:29               ` Robert J. Chassell
2006-01-16 14:15               ` Richard M. Stallman
2006-01-21 13:01                 ` Eli Zaretskii
2006-01-23  0:09   ` Alex Schroeder
2006-01-27 18:48     ` Eli Zaretskii

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/emacs/

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

  git send-email \
    --in-reply-to=9abbd5730601130610w4507670aqd122cb33bc564486@mail.gmail.com \
    --to=kensanata@gmail.com \
    --cc=bkhl@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    --cc=rcyeske@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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