unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Francis Southern <francis.southern@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: Typos in the manual
Date: Wed, 16 Feb 2011 23:46:22 +0000	[thread overview]
Message-ID: <87zkpvwnjl.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <AANLkTi=CeZgbK_qatbZ4UioqhDS42yoiUdpCDDxV92WA@mail.gmail.com> (Francis Southern's message of "Tue, 15 Feb 2011 21:30:41 -0600")

Francis Southern <francis.southern@gmail.com> writes:

> On 15 February 2011 20:43, Mark Harig <idirectscm@aim.com> wrote:
>>
>> 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.
>>
>
> While I agree that a consistent style is desirable for a manual,

You know, actually I disagree with that.

The Guile manual is around 800 pages long, and I think it does no harm
at all to have a little variability, or for different voices to come
through here and there.

It's important for the technical material to be correct and clearly
described, of course.  In my view the other two high level requirements
are that there should be an overall sense of narrative through the
manual, and that any individual section or related group of sections
should read well in their own context.

Clearly, in the world in general, there are significant forces that
encourage closely following a consistent style: basically all commercial
organisations, and in particular journalism.  But I think that's because
they are big organisations with lots of people, and it's easier overall
to lay down rules than to apply judgement in each case.  As things stand
at the moment, I don't think that needs to apply to the Guile manual.

> I
> just wanted to point out that the issue at hand is definitely not a
> British vs. American English debate.
> For example, although he has nothing to say on the matter (that I
> could find), you'll notice that H.W. Fowler quite consistently uses a
> comma after "i.e." and "e.g." in his book, "The King's English" [0].
> I sincerely doubt that anyone would dare to call his English
> Americanised.

Thanks.  And another big British pro-comma reference is the Economist's
style guide.

So I accept that, democratically speaking, I've lost the argument.
Nevertheless, this isn't something that I personally want to spend time
on.  I think there's loads more important stuff to review and improve in
the manual, and I'd rather focus on that.  On the other hand, if there
are more contributors on board in future, and one of them wants to work
on this, I won't object.

I hope that we are now approaching a point where the manual is
technically complete and correct, so please - anyone looking at the
manual - do regard it all as fair game, report any mistakes or problems
in understanding, check that the examples actually work, and so on.

Regards,
       Neil



  reply	other threads:[~2011-02-16 23:46 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
2011-02-16  3:30             ` Francis Southern
2011-02-16 23:46               ` Neil Jerram [this message]
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=87zkpvwnjl.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    --cc=francis.southern@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.
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).