From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: gettext: commands/*
Date: Mon, 21 Dec 2009 10:17:22 -0600 [thread overview]
Message-ID: <4B2F9F92.2020203@gmail.com> (raw)
In-Reply-To: <20091221123734.GE5847@riva.ucam.org>
Colin Watson wrote:
> On Mon, Dec 21, 2009 at 01:16:04PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> === modified file 'commands/halt.c'
>> --- commands/halt.c 2009-12-03 23:07:29 +0000
>> +++ commands/halt.c 2009-12-21 00:10:33 +0000
>> @@ -35,7 +35,7 @@ static grub_command_t cmd;
>> GRUB_MOD_INIT(halt)
>> {
>> cmd = grub_register_command ("halt", grub_cmd_halt,
>> - 0, "halts the computer. This command does not"
>> + 0, "Halts the computer. This command does not"
>> " work on all firmware.");
>> I would rather say "On *every* firmware."
>
> That doesn't sound grammatical to this native speaker, because you use
> "every" with singular count nouns and "firmware" isn't pluralisable -
> I'm not sure of its exact grammatical category but it feels like a mass
> noun to me. Besides, "does not work on all" feels more idiomatically
> correct than "does not work on every".
>
> "All firmware" is definitely better, but you could use "all firmware
> implementations" if you wanted to be crystal-clear.
I believe it would be also correct to say
This command does not work on some firmware implementations.
-- Bruce
next prev parent reply other threads:[~2009-12-21 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 18:22 gettext: commands/* Carles Pina i Estany
2009-12-07 0:49 ` Carles Pina i Estany
2009-12-07 8:44 ` Carles Pina i Estany
2009-12-07 23:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-21 0:21 ` Carles Pina i Estany
2009-12-21 0:47 ` Carles Pina i Estany
2009-12-21 12:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-21 12:37 ` Colin Watson
2009-12-21 16:17 ` Bruce Dubbs [this message]
2009-12-24 21:03 ` Robert Millan
2009-12-21 22:13 ` Carles Pina i Estany
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=4B2F9F92.2020203@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=grub-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.