From: Mark Harig <idirectscm@aim.com>
To: neil@ossau.uklinux.net
Cc: bug-guile@gnu.org, Ralf.Wildenhues@gmx.de
Subject: Re: Typos in the manual
Date: Tue, 15 Feb 2011 21:43:13 -0500 [thread overview]
Message-ID: <8CD9B9A6430A5CE-714-4AA4@webmail-d099.sysops.aol.com> (raw)
In-Reply-To: <87mxlw7s3i.fsf@ossau.uklinux.net>
> >> Also, while the Chicago Manual of Style recommends it, some other
> > online
> >> grammar sites mention that it is American English style, but
British
> >> English would not add a comma afterwards.
>
> My feeling is consistent with that. I'm British, and I'd say there
are
> lots of cases where it is more natural (to me) not to have a comma
after
> "i.e." or "e.g.".
>
This is the crux of the argument. Should the GNU Guile manual be
written using British English or American English, both in grammar and
spelling? American English usage rules require a comma, while British
English requires that there not to be a comma. There needs to be a
decision about which set of usage rules should be used in the primary
version of the manual, and then differences can be resolved in
translations. But whichever is decided, it should not be "use a comma
if you feel it's needed; otherwise, leave it out." Reference manuals
are not the place for personal style. Let's leave that for tutorials.
--
next prev parent reply other threads:[~2011-02-16 2:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:25 Typos in the manual Ralf Wildenhues
2011-02-13 0:49 ` Neil Jerram
2011-02-13 7:00 ` Ralf Wildenhues
2011-02-13 22:29 ` Neil Jerram
2011-02-15 15:48 ` Marijn
2011-02-15 20:21 ` Mark Harig
2011-02-15 23:55 ` Neil Jerram
2011-02-16 0:52 ` Mark Harig
2011-02-16 22:37 ` Neil Jerram
2011-02-15 23:49 ` Neil Jerram
2011-02-15 20:48 ` Mark Harig
2011-02-15 21:14 ` Ralf Wildenhues
2011-02-15 22:32 ` Mark Harig
2011-02-16 0:14 ` Neil Jerram
2011-02-16 2:43 ` Mark Harig [this message]
2011-02-16 3:30 ` Francis Southern
2011-02-16 23:46 ` Neil Jerram
2011-02-16 3:03 ` Mark Harig
2011-02-16 8:18 ` Thien-Thi Nguyen
2011-02-17 0:10 ` Neil Jerram
2011-02-17 1:21 ` Mark Harig
2011-02-16 21:17 ` Ludovic Courtès
2011-02-17 0:14 ` Neil Jerram
2011-02-17 3:13 ` Mark Harig
2011-02-17 11:33 ` Andy Wingo
2011-02-21 20:23 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2011-02-19 17:40 Bruno Haible
2011-02-19 17:56 ` Ralf Wildenhues
2011-02-24 23:31 ` Ludovic Courtès
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=8CD9B9A6430A5CE-714-4AA4@webmail-d099.sysops.aol.com \
--to=idirectscm@aim.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.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 read-only IMAP folder(s) and NNTP newsgroup(s).