From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] I can RTFM, but can I understand it: re elog messages
Date: Fri, 20 Aug 2010 15:58:21 +0100 [thread overview]
Message-ID: <201008201558.21825.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <4C6E8123.30301@gmail.com>
On Friday 20 August 2010 14:20:35 Bill Longman wrote:
> On 08/19/2010 04:38 PM, Peter Humphrey wrote:
> > On Thursday 19 August 2010 21:21:20 Kevin O'Gorman wrote:
> >> So I looked up "auto-hinter" in the flagedit(1) program. It says:
> >> auto-hinter: Local Flag: Use the unpatented auto-hinter instead
> >> of the (recommended) TrueType bytecode interpreter (media-
> >> libs/freetype)
> >>
> >> The placement of the "(recommended)" is just a bit ambiguous.
> >
> > No, it isn't. You may be being confused by the unnecessary
> > inclusion of brackets (parentheses if you're American); remove
> > them and you see that the TrueType byte-code interpreter is
> > recommended. Or, just consider the phrase "the recommended
> > TrueType bytecode interpreter", with or without brackets. I can't
> > see how that could be thought ambiguous.
>
> I have to agree it's ambiguous. You have to wonder why the
> parenthetical "recommended" is offset if it's just part of the
> sentence. If it were as you say, there would be no need to put them
> there. As it is written it sounds like it's making an aside claiming
> that one of them is recommended and, by its placement, it's hard to
> discern its antecedent.
Its placement puts it squarely with the noun phrase following it. To
associate it with the preceding one instead would be perverse. (Just to
continue flogging a dead horse...) :-)
I agree though that the brackets are neither necessary nor helpful.
--
Rgds
Peter. Linux Counter 5290, 1994-04-23.
next prev parent reply other threads:[~2010-08-20 15:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:21 [gentoo-user] I can RTFM, but can I understand it: re elog messages Kevin O'Gorman
2010-08-19 22:01 ` Neil Bothwick
2010-08-19 23:38 ` Peter Humphrey
2010-08-20 7:20 ` Dale
2010-08-20 8:01 ` Neil Bothwick
2010-08-20 8:39 ` Dale
2010-08-20 8:03 ` Neil Bothwick
2010-08-20 9:01 ` Alan McKinnon
2010-08-20 9:23 ` Neil Bothwick
2010-08-20 14:53 ` Peter Humphrey
2010-09-02 16:15 ` Neil Bothwick
2010-08-20 9:06 ` Alan McKinnon
2010-08-20 13:20 ` Bill Longman
2010-08-20 14:58 ` Peter Humphrey [this message]
2010-08-20 15:12 ` Bill Longman
2010-08-20 15:40 ` Kevin O'Gorman
2010-08-20 17:07 ` [WAY OT] Parenthese, was " Mike Edenfield
2010-08-20 19:00 ` Alan McKinnon
2010-08-20 19:32 ` [gentoo-user] Re: [WAY OT] Parenthese Alex Schuster
2010-08-20 20:14 ` Alan McKinnon
2010-08-21 9:53 ` Peter Humphrey
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=201008201558.21825.peter@humphrey.ukfsn.org \
--to=peter@humphrey.ukfsn.org \
--cc=gentoo-user@lists.gentoo.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