git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Adam" <thomas.adam22@gmail.com>
To: "Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/6] manual: Fix or remove em dashes.
Date: Tue, 9 Oct 2007 23:02:01 +0100	[thread overview]
Message-ID: <18071eea0710091502y3b70231dnd4270a3155af91a8@mail.gmail.com> (raw)
In-Reply-To: <20071009215255.GB3146@ins.uni-bonn.de>

On 09/10/2007, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> Hello, and sorry, this patch should be number 6/6 of course.
>
> * Thomas Adam wrote on Tue, Oct 09, 2007 at 11:41:41PM CEST:
> > On 09/10/2007, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> > > em dashes were used inconsistently in the manual.
> > > This changes them to the way they are used in US English.
> >
> > I find this particular patch to be rather odd; there is nothing
> > invalid in the way the em-dashes are used.
>
> No, not invalid, just inconsistent usage in the manual.
>
> > Why is it US English is somehow de facto over, say, proper English?
> > :)
>
> Oh, that was written quoting from memory and experience.  But here's a
> quote to back it up, from <http://en.wikipedia.org/wiki/Dash> as of now:
>
> | According to most American sources (e.g., The Chicago Manual of Style)
> | and to some British sources (e.g., The Oxford Guide to Style), an em
> | dash should always be set closed (not surrounded by spaces). But the
> | practice in many parts of the English-speaking world[...] sets it
> | open [...]
>
> No, I did not write that!  ;-)

Well, I don't see why it needs to change, to be honest.  I use
em-dashes all the time surrounded by spaces, as do many academics.
The fact that may here in the UK do not use the letter z in place of s
to satisfy the OSD is also of equal testament to this.

-- Thomas Adam

      reply	other threads:[~2007-10-09 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 20:57 [PATCH 0/6] Some small documentation fixes Ralf Wildenhues
2007-10-09 21:00 ` [PATCH 1/6] Fix some typos, punctuation, missing words, minor markup Ralf Wildenhues
2007-10-09 21:01 ` [PATCH 2/6] Fix wording in push definition Ralf Wildenhues
2007-10-09 21:02 ` [PATCH 3/6] manual: Fix example finding commits referencing given content Ralf Wildenhues
2007-10-09 21:03 ` [PATCH 4/6] manual: add some markup Ralf Wildenhues
2007-10-09 21:03 ` [PATCH 5/6] manual: use 'URL' instead of 'url' Ralf Wildenhues
2007-10-09 21:05 ` [PATCH 0/6] manual: Fix or remove em dashes Ralf Wildenhues
2007-10-09 21:41   ` Thomas Adam
2007-10-09 21:52     ` Ralf Wildenhues
2007-10-09 22:02       ` Thomas Adam [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

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

  git send-email \
    --in-reply-to=18071eea0710091502y3b70231dnd4270a3155af91a8@mail.gmail.com \
    --to=thomas.adam22@gmail.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).