All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@paralogos.com>
To: zhangfx@lemote.com, gnewsense-dev@nongnu.org,
	linux-mips@linux-mips.org, loongson@bjlx.org.cn, yanh@lemote.com
Subject: Re: yeloong or yeeloong
Date: Wed, 01 Apr 2009 11:16:31 +0200	[thread overview]
Message-ID: <49D330EF.1000209@paralogos.com> (raw)
In-Reply-To: <20090331175252.GB4918@adriano.hkcable.com.hk>

Zhang Le wrote:
> Sorry for cross posting, but I just want to bring this issue to a wider
> audience.
>
>
>   2. Yeeloong -> Yeloong. 
>
>     I think this one is controversial. The e in Yeloong, to me, sounds like e
>     in yes, not ee in eel. So that the sound is changed, this action is by
>     itself bad. And Yeloong may make people connect it with the word yell,
>     which is not quite good a word. Moreover, the original sound is more like 
>     its Chinese brand name.
>   
For whatever it's worth, please note that the general rule in English is
for "e" to be "long", as in "me" or "eel", whenever there is a single
consonant before the next vowel, and for it to be "short", as in "them"
or "yell", when followed by multiple consonants before the next vowel. 
There are, of course, many, many exceptions in English to the general
pronunciation rules, but by default "yeeloong" and "yeloong" would be
pronounced about the same.  The only reason to have the extra "e" in
"yeelong" in a transliteration to English would be to emphasize a long,
drawn out "ee" sound.  To have the "yell" sound, one would spell it
"yelloong", with two l's. Worst case, the single "e" in "yeloong" would
be collapsed to a "schwa" vowel, more of a short "uh" than an "eh", the
way Americans often do with "the" (or "Lemote").

This is what happens when you ask someone who majored in computer
science but minored in poetry! ;o)

          Regards,

          Kevin K.

      parent reply	other threads:[~2009-04-01  9:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15359.159.226.43.42.1238459390.squirrel@mail.lemote.com>
2009-03-31 17:52 ` yeloong or yeeloong Zhang Le
2009-04-01  0:34   ` yanhua
2009-04-01  1:46   ` yanhua
2009-04-01  4:19   ` fxzhang
2009-04-01  9:30     ` Zhang Le
2009-04-01  9:16   ` Kevin D. Kissell [this message]

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=49D330EF.1000209@paralogos.com \
    --to=kevink@paralogos.com \
    --cc=gnewsense-dev@nongnu.org \
    --cc=linux-mips@linux-mips.org \
    --cc=loongson@bjlx.org.cn \
    --cc=yanh@lemote.com \
    --cc=zhangfx@lemote.com \
    /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.