From: Ken Raeburn <raeburn@raeburn.org>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: compiler.texi: Compiling to the virtual machine
Date: Mon, 19 Jan 2009 15:43:30 -0500 [thread overview]
Message-ID: <BEDE2AB2-4859-40B0-BE58-EE3C4425F4FA@raeburn.org> (raw)
In-Reply-To: <87d4elr0gs.fsf@gnu.org>
On Jan 17, 2009, at 18:12, Ludovic Courtès wrote:
>>> s/e.g./e.g.,/
>>
>> To me, s/e.g./for example/ is an idempotent transformation. So if the
>> clause after "e.g." is short, no comma necessary. Otherwise you
>> need a
>> comma for breath. But maybe it is a snooty style.
>
> I dunno, I thought the comma was sort of compulsory.
>
> A quick googling reveals that opinions diverge, but that the comma
> after
> "e.g." is often used in American English.
My understanding is that in American usage you always put in the
comma; leaving it out (and sometimes the periods as well) seems to be
more common in British usage. (Actually, I suspect that technically a
comma should be required with "for example" as well, regardless of the
author's breathing patterns; I've seen at least one style guide
supporting that.) What I've seen vary more is whether "i.e." and
"e.g.", as (abbreviations for) Latin, should be italicized. I
generally use italics, in a medium that permits it, and always learned
to do it that way, but I've seen at least one style guide recently
that says not to bother.
Does the FSF have a style guide for this sort of thing?
... Okay, I just pulled up the GNU Coding Standards document, which
says nothing about this but use "e.g." always in Roman or bold (in
code examples) and with inconsistent comma usage (present in text,
absent in code examples, so they may have been written by different
people without attention to that detail), and "A Style Guide for GNU
Documentation" (http://www.gnu.org/doc/Press-use/GNU-Press-styleguide.pdf
) which also fails to address this or to even use "e.g." or "i.e.",
but uses "etc." in plain Roman, and specifically says to use only
logical markup, not typographical markup, with the one exception of @r
"to cause plain, explanatory text in a table or example to be in a
Roman font." Since they don't touch on "e.g."/"i.e."/"etc." usage in
the text, and the specific guideline elsewhere is "italic" and not
"strong" or "emphasized", I wonder if what's written is really the
intent or if they just didn't think of these cases.
Ken
prev parent reply other threads:[~2009-01-19 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 17:37 compiler.texi: Compiling to the virtual machine Andy Wingo
2009-01-13 22:45 ` Ludovic Courtès
2009-01-15 22:03 ` Andy Wingo
2009-01-17 23:12 ` Ludovic Courtès
2009-01-19 20:43 ` Ken Raeburn [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
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=BEDE2AB2-4859-40B0-BE58-EE3C4425F4FA@raeburn.org \
--to=raeburn@raeburn.org \
--cc=guile-devel@gnu.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.
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).