From: Randy Dunlap <rdunlap@xenotime.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Michael Opdenacker <michael-lists@free-electrons.com>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 2.6.18] [TRIVIAL] Spelling fixes in Documentation/DocBook
Date: Sat, 23 Sep 2006 10:04:28 -0700 [thread overview]
Message-ID: <20060923100428.99baa1ad.rdunlap@xenotime.net> (raw)
In-Reply-To: <1159005072.24527.891.camel@pmac.infradead.org>
On Sat, 23 Sep 2006 10:51:12 +0100 David Woodhouse wrote:
> On Thu, 2006-09-21 at 23:18 +0200, Michael Opdenacker wrote:
> > -and associated transciever to support <emphasis>Dual-Role</emphasis>
> > +and associated transceiver to support <emphasis>Dual-Role</emphasis>
>
> Since you're actually touching this line already, could you not fix
> 'Role' to 'Rôle'? If you fix the aspell config it ought to catch that
> error too.
>
> Our computers became capable of more than just ASCII text some years ago
> -- there's no real excuse for dropping accents any more.
On this side of the pond, many words lose their diacritical marks
after lots of usage. "Cooperate" has previously been hyphenated
(co-operate) or spelled with a diaeresis over the second 'o'.
They are now lost. So we can thank teletypes for that?
or laziness? could be.
Anyway, "Role" looks good to me.
---
~Randy
next prev parent reply other threads:[~2006-09-23 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 21:18 Michael Opdenacker
2006-09-21 22:07 ` Randy.Dunlap
2006-09-23 18:55 ` Michael Opdenacker
2006-09-22 16:34 ` Alan Cox
2006-09-22 16:36 ` Randy.Dunlap
2006-09-22 19:10 ` Alan Cox
2006-09-23 19:07 ` Michael Opdenacker
2006-09-23 21:02 ` Alan Cox
2006-09-23 9:51 ` David Woodhouse
2006-09-23 17:04 ` Randy Dunlap [this message]
2006-09-23 18:31 ` Lee Revell
2006-09-23 18:33 ` David Woodhouse
2006-09-23 18:47 ` Lee Revell
2006-09-23 19:32 ` Alan Cox
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=20060923100428.99baa1ad.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael-lists@free-electrons.com \
--cc=trivial@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
all inboxes | Powered by JetHome®