Here's one vote for "Arial" to rhyme with "aerial" (or Ariel, the Little
Mermaid, and "Unicode" as yoo-nih-kohd (like "unicycle" or "unilateral";
you would never say yoo-nee in either case).
Although why anyone wants to know how a native Southern California
speaker pronounces things is REALLY bey
On Fri, Jul 14, 2000 at 14:33:53 -0800, Tex Texin wrote:
> And do we know which locale we are debating the pronounciation of?
> Michael is in Ireland, ...
My manager, native Irish (she's absolutely lovely person - the best
boss I ever had), would pronounce it with final /kozh/ I think ;-)
In Ru
Can we settle "tomato" and "potato" before we get into more recent
terminology?
And do we know which locale we are debating the pronounciation of?
Michael is in Ireland, not sure where John hangs his hat.
Maybe "Unicode" should be in the locale of San Jose, as its point of
origin?
Michael Everso
I shouldn't have used "header". What I meant is not the message header in
the RFC 822 sense but the information out of the header that gets copied
into the message BODY on a reply.
Example right below.
-Original Message-
From: John Cowan [mailto:[EMAIL PROTECTED]]
Sent: Friday, July
on 7/14/2000 8:41 AM, Shigeki Moro <[EMAIL PROTECTED]> wrote:
> I often use Arial Unicode MS font to display texts in Unicode,
> but I don't know the pronunciation of "Arial". How do we
> pronounce it? 'eirial' or 'araial'?
To answer the poor man's original question, the Japanese-style pronuncia
Ar 13:03 -0800 2000-07-14, scríobh John Cowan:
>I am using U+0027 to represent U+02C8, which is always to be placed before the
>syllable to which it attaches. To me, [ju 'ni kowd] would suggest
>an etymology for "Unicode" from "unique code".
Yes, but it is the Universal Character Set. "uni-" as
Ar 09:04 -0800 2000-07-14, scríobh John H. Jenkins:
>Personally, I don't much care, particularly considering the fact that
>we can't agree on a pronunciation of "Unicode."
I prefer ['ju:nIko:d]. I dislike it when it's pronounced ['ju:ni:,ko:d].
Cf. Universe. Though of course why any of you shoul
On Fri, 14 Jul 2000, Ayers, Mike wrote:
> Thanks. Storing the bitmaps of the entire string might be better
> for a very small number of display strings. My solution was designed for an
> intermediate number of strings where memory would be saved by encding
> multiply-used characters one
"John H. Jenkins" wrote:
> There are distinct ['ju ni kowd] and ['ju n@ kowd] camps, as well as
> a small [ju 'ni kowd] contingent (if I understand your transcription
> correctly).
I am using U+0027 to represent U+02C8, which is always to be placed before the
syllable to which it attaches. To m
At 12:01 PM -0800 7/14/00, John Cowan wrote:
>"John H. Jenkins" wrote:
>
>> [W]e can't agree on a pronunciation of "Unicode."
>
>What are the usual alternatives? I used to say ['ju ni kowd], but my wife
>complained that this made me sound like a hick, and I changed to
>['ju n@ kowd].
>Consideri
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, July 15, 2000 5:09 AM
>
> This assumes that the only support required is output of previously
> translated internal messages. If *that's* the case, you can
> usually save
> even more memory by using a run-length encoded "pic
"John H. Jenkins" wrote:
> [W]e can't agree on a pronunciation of "Unicode."
What are the usual alternatives? I used to say ['ju ni kowd], but my wife
complained that this made me sound like a hick, and I changed to ['ju n@ kowd].
Considering that the Unix text editor "vi" can be pronounced ['v
[EMAIL PROTECTED] wrote:
> "If an all kana Japanese document is read aloud, there will be places that are
> ambiguous and hard (may be impossible) to understand"
>
> When a typical Japanese (written in kanji + kana) is read aloud, the reader
> knows where to put accent, tonation and pause, but n
I would say:
"If an all kana Japanese document is read aloud, there will be places that are
ambiguous and hard (may be impossible) to understand"
When a typical Japanese (written in kanji + kana) is read aloud, the reader
knows where to put accent, tonation and pause, but not so with an all kana
John Cowan asked:
> [EMAIL PROTECTED] wrote:
>
> > The problem with all kana (or all Roman ch) document is because there are so
> > many words with same pronounciations. For example, the Roman Characters "KAMI"
> > may mean God, or hair, or paper, or above. "HASHI" may mean bridge or chop
> > st
This assumes that the only support required is output of previously
translated internal messages. If *that's* the case, you can usually save
even more memory by using a run-length encoded "picture" of the bitmap on
the display (in fact, I suggested exactly that solution for a, shall we
say, "close
[EMAIL PROTECTED] wrote:
> The problem with all kana (or all Roman ch) document is because there are so
> many words with same pronounciations. For example, the Roman Characters "KAMI"
> may mean God, or hair, or paper, or above. "HASHI" may mean bridge or chop
> sticks. If it is written in kanji
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 13, 2000 12:11 PM
> To: Unicode List
> Cc: [EMAIL PROTECTED]
> Subject: RE: Subset of Unicode to represent Japanese Kanji?
>
>
> Kevin Bracey wrote:
> > -
Otto Stolz wrote:
So, I guess, a limited-capability device can
> support Katakana only, and an advanced one has to support Kanji + Hiragana
> + Katakana.
In practice, standard Japanese display devices have to handle Latin text too;
e.g. the word transcribed "ooeru" in romaji is usually written
At 7:41 AM -0800 7/14/00, Shigeki Moro wrote:
>Dear Listmembers,
>
>I often use Arial Unicode MS font to display texts in Unicode,
>but I don't know the pronunciation of "Arial". How do we
>pronounce it? 'eirial' or 'araial'?
>
Personally, I don't much care, particularly considering the fact that
Gregg Reynolds wrote:
> What counts (no pun intended) is the
> mathematical rule of evaluation, which says that the LSD position is ones,
> the next over is tens, then hundreds, etc.
That is no rule at all, but a tautology. If we wrote one hundred twenty three
as 321, the "3" would be in the LS
Chris Wendt wrote:
> This is relevant when you are running with a non-English OS locale. It will
> prevent entering non-usascii characters for day and month names in the reply
> header so as to not force you to send in UTF-8 in case you write in a
> different script than the OS locale is.
How's
Dear Listmembers,
I often use Arial Unicode MS font to display texts in Unicode,
but I don't know the pronunciation of "Arial". How do we
pronounce it? 'eirial' or 'araial'?
Thanks in advance,
Shigeki Moro
[EMAIL PROTECTED]
http://www.ya.sakura.ne.jp/~moro/
Whups. I had just noticed how I'd typed it myself.
Addison
On Fri, 14 Jul 2000, Doug Ewell wrote:
> Addison P. Phillips <[EMAIL PROTECTED]> wrote:
>
> > You do need to include a Byte Order Mark character as the first pair
> > of bytes in the file (that would be character U+FFFE)
>
> No, it's
- Original Message -
From: "Akil Fahd" <[EMAIL PROTECTED]>
> How can I convert from cp 1256 to unicode, without doing it character by
> character? Is there software that will do this?
When you say Unicode, I assume you mean UTF-8? If you are using a program
like FrontPage, converting to U
I'am trying to create a bilingual and bi-directional (Arabic and English
Qur'an)e-Book, that will be compliant with the Open eBook OEB specification.
This is targeted at the PalmOS, but should be renderable in XML and/or
XHTML compliant browsers such IE 5.0 and Netscape 6.0 or any type of Ope
Kevin Bracey wrote:
> Obviously one of your competitor's products I saw then :)
> Seriously though,
> you're right - a modern till is often a DOS box or something
> with a full CRT,
> so can be expected to handle kanji. 5 or 10 years ago it
> would have been
> a different question.
Well, I hat
In message <[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote:
>
> Horror! Abomination! Heresy! ;-)
>
> I don't care for mididisc players but, hey, software for *shop tills* needs
> full-fledged i18n. And the Japanese version must support all the kanjis
> that might be needed in the descript
[EMAIL PROTECTED] wrote:
> Whether its practical or not to have an all kana display
> depends on your
> application. As Kevin Bracey said, things as shop tills, and
> minidisc players
> displaying track names may be OK, since the contents are focused.
Horror! Abomination! Heresy! ;-)
I don't c
Dear Roozbeh;
In Arabic and Arabic Extended Languages like Pashto, Farsi, Urud and
many other I think we need to talk about Standardization, of certin issues
specially the Fonts, due to UNICODE which are now possible to be used
by several languages. An Arabic Font developer can just Add 6 other
c
30 matches
Mail list logo
