That agrees with the results I get on http://www.macchiato.com/unicode/convert.html.
Mark
- Original Message -
From:
J.
William Semich
To: Mark Davis ; Rick H Wesson
Cc: Unicore ; Unicode ; w3c-i18n-ig
Sent: Wednesday, November 15, 2000
22:46
Subject: Re:
Bjorn Stabell [EMAIL PROTECTED] wrote:
According to this news item (in Chinese), China rejected HK's
application to use Unicode, and instead says they have to use
ISO 10646-1:2000 or GB18030. Apparently they don't like to
standardize on a standard controlled by an organization of
Dear All,
I have serious problems with Unicode Arabic. The main problem is with the
Arabic shaping rules in TUS 3.0, pages 192--197. I think these should be
changed in some suggested ways. Would someone please guide me on how
should I prepare an official suggestion?
1. "Bidi and Cursive
The only question I have here is that no one was *ever* suggesting a slash
be used for the decimal separator. The suggestion was made for the CURRENCY
separator. Since the question was asked (and all of the answers were made)
mentioning the decimal separator only, I would have to wonder whether
At 4:44 PM -0800 11/15/00, Markus Scherer wrote:
In the case of Java, the equivalent course of action would be to
stick with a 16-bit char as the base type for strings. The int type
could be used in _additional_ APIs for single Unicode code points,
deprecating the old APIs with char.
It's
On Thu, 16 Nov 2000, Michael (michka) Kaplan wrote:
The only question I have here is that no one was *ever* suggesting a slash
be used for the decimal separator. The suggestion was made for the CURRENCY
separator. Since the question was asked (and all of the answers were made)
mentioning
On Thu, Nov 16, 2000 at 05:58:27 -0800, Elliotte Rusty Harold wrote:
public char charAt(int index)
This method is used to walk strings, looking at each character in
turn, a useful thing to do. Clearly it would be possible to replace
it with a method with a String return type like this:
At 7:26 AM -0800 11/16/00, Valeriy E. Ushakov wrote:
On Thu, Nov 16, 2000 at 05:58:27 -0800, Elliotte Rusty Harold wrote:
public char charAt(int index)
This method is used to walk strings, looking at each character in
turn, a useful thing to do. Clearly it would be possible to replace
I would openly encourage you to help "perpetuate the evidence" so that this
change can be evaluated and the right thing can be done in MS products
(which as I said currently have the slash as a currency sign). Cites and
sources for the investigation, etc. would be very important here.
I do not
On Thu, 16 Nov 2000, Michael (michka) Kaplan wrote:
I would openly encourage you to help "perpetuate the evidence" so that this
change can be evaluated and the right thing can be done in MS products
(which as I said currently have the slash as a currency sign). Cites and
sources for the
There is no legal Farsi 32-bit version of Windows available in Iran, but
there was once a 16-bit one available. BTW, it depends on how do you
interpret legal. Iran is not in the international copyright agreement, so
doing a localized Windows is considered legal here. There are more
On Thu, 16 Nov 2000, John Cowan wrote:
If the copy cannot show a lawful chain of licensing from Microsoft,
then it cannot be sold in Berne Convention countries (i.e. most of the
world).
This seems reasonable.
I think the point is that some day there will be a licensed Persian Windows,
On Thu, 16 Nov 2000, Markus Scherer wrote:
The ICU API was changed this way within a few months this year. Some of the
higher-level implementations are still to follow until next summer, when there will
be some 45000 CJK characters that will be infrequent but hard to ignore - the Chinese
and
Juliusz Chroboczek wrote:
I believe that Java strings use UTF-8 internally.
.class files use a _modified_ utf-8. at runtime, strings are always in 16-bit unicode.
At any rate the
internal implementation is not exposed to applications -- note that
`length' is a method in class String (while
... but I have fat fingers today, and the difference betwixt Ctrl-C
(cancel) and Ctrl-X (send) is pretty small.
In any case, if you bothered to read my ruminations, your comments on the
dilemma are welcome.
Best Regards,
Addison
===
Normally this thread would be of only academic interest to me...
...but this week I'm writing a spec for adding Unicode support to an
embedded operating system written in C. Due to Mssrs. O'Conner and
Scherer's presentations at the most recent IUC, I was aware of the clash
between internal
Microsoft never disclosed Windows source code for localization into
Farsi. We once developed a Farsi version of Windows 3.1 entirely
in-house and shipped it to Iran. We used a vendor for localization but
source bits were never sent to Iran. That product was protected by a
dongle which probably
We have found that it works pretty well to have a uchar32 datatype, with
uchar16 storage in strings. In ICU (C version) we use macros for efficient
access; in ICU (C++) version we use method calls, and for ICU (Java version)
we have a set of utility static methods (since we can't add to the Java
18 matches
Mail list logo
