From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: michael.opdenacker@bootlin.com,
"Ulrich Ölmann" <u.oelmann@pengutronix.de>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] ref-manual: document Rust classes
Date: Mon, 16 Jan 2023 16:34:31 +0000 [thread overview]
Message-ID: <313f2f809ffb451062547e7c5438a82173549d09.camel@linuxfoundation.org> (raw)
In-Reply-To: <173AD6377FCD14EA.23170@lists.yoctoproject.org>
On Mon, 2023-01-16 at 16:15 +0000, Richard Purdie via
lists.yoctoproject.org wrote:
> On Mon, 2023-01-16 at 17:05 +0100, Michael Opdenacker via
> lists.yoctoproject.org wrote:
> > Hi Ulrich,
> >
> > On 16.01.23 at 08:35, Ulrich Ölmann wrote:
> > > Hi Michael,
> > >
> > > I am no inhabitant of the rust world, so I can not evaluate the
> > > technical content
> >
> >
> > That's not very different from my status. I'm just a tourist to the Rust
> > world so far ;-)
> >
> > > s/and an ``src``/and a ``src``/
> >
> >
> > I'd disagree on this one. If you read "src", what you pronounce ("S. R.
> > C.") starts with a vowel, hence the use of "an".
> >
> > https://editorsmanual.com/articles/indefinite-article-a-an-with-abbreviations/
> > seems to agree with me, but I'd be happy to be corrected!
> >
> > Thanks for the proofreading!
>
> As a native speaker, it is definitely "a source" or "a src", "an src"
> just sounds plain wrong to me!
I was thinking a bit more about this, I think the reason is that you'd
always pronounce this as "source", I'm not sure how you'd say "src" out
loud! :)
Cheers,
Richard
next prev parent reply other threads:[~2023-01-16 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 18:09 [PATCH] ref-manual: document Rust classes michael.opdenacker
2023-01-15 20:03 ` [docs] " Alex Kiernan
2023-01-15 20:09 ` Alexander Kanavin
2023-01-16 17:18 ` Michael Opdenacker
2023-01-16 19:30 ` Alex Kiernan
2023-02-02 18:06 ` Michael Opdenacker
2023-02-03 9:42 ` Michael Opdenacker
2023-02-03 12:06 ` Alex Kiernan
2023-02-03 17:32 ` Michael Opdenacker
2023-01-16 7:35 ` Ulrich Ölmann
2023-01-16 16:05 ` Michael Opdenacker
2023-01-16 16:15 ` Richard Purdie
[not found] ` <173AD6377FCD14EA.23170@lists.yoctoproject.org>
2023-01-16 16:34 ` Richard Purdie [this message]
2023-01-16 17:08 ` Michael Opdenacker
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=313f2f809ffb451062547e7c5438a82173549d09.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=u.oelmann@pengutronix.de \
/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