On Thu, Apr 13, 2017 at 10:13:40AM +0300, Lars Wirzenius wrote:
> On Thu, Apr 13, 2017 at 08:59:30AM +0200, Wouter Verhelst wrote:
> > On Wed, Apr 12, 2017 at 10:16:18PM +0100, Jonathan Dowland wrote:
> > > On Wed, Apr 12, 2017 at 03:35:46PM +0200, Bastien ROUCARIES wrote:
> > > > Subject: Re: Bug#860170: node-brfs -- browserify fs.readFileSync() 
> > > > static asset inliner
> > > 
> > > This should have "ITP" in the title of the bug.
> 
> Best achieved by using reportbug, which gets all the details right so
> that those who need to, can filter out WNPP related bug reports.
> 
> > > > Browserify is an JavaScript tool (compiler) that allows developers
> > >                 ^^^^
> > > 
> > > should be "a", "an" is used if the following word begins with a vowel.
> > 
> > (or the letter h followed by a vowel)
> 
> A hat, a hotel. a helmet. Unless the speaker has a dialect where
> they're an hat ("an 'at"), etc. It seems Cockney is one such dialect.

Yes, you're right of course. I was thinking of a specific example (don't
remember which one anymore) where the word was *written* with an H at
the start, but the H was not pronounced; I just wrote it down
incorrectly.

> I'm not a native speaker. The rule I was taught is "it's an if the
> next word starts with a vowel _sound_ when spoken".

Yup, indeed, that's the one.

The sillyness about this is that you're making rules about *writing*
something that depend on something that has *nothing* to do with
actually writing things.

Do you write "An RTC server" or "A RTC server"? Well, that depends on
whether you say "An arr-tee-cee" or "A real-time communication". It's
horrible as a rule.

> English is too complicated. We should all switch to Finnish instead.
> Free Finnish lessons at Debconf. Lipputangonnuppi.

Free (introduction to) Dutch lessons, too!

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
       people in the world who think they really understand all of its rules,
       and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

Reply via email to