I remember being shown in the ECMA bidi WG a document from China that specified
the use of the Arabic script for Kazakh (I think it was Kazakh), which was
somewhat different from ISO-8859-6 and ASMO. I remember they had fewer shapes.
Jony
> -Original Message-
> From: Michael (michka) Kap
Most of these characters came from existing standards that were included in
Unicode, rather than separately requested character additions. There are
some exceptions for Cyrillic, and possibly for Arabic but that one I am not
100% sure about.
But most of them have been there all along based on com
Hello,
I'm writing an article about history of Kazakh and other Turkic alphabets.
Could you help me with history of their inclusion in Unicode?
Who have proposed characters which are specific for Kazakh and all other
Turkic languages in Arabic, Latin and Cyrillic scripts? How I can contact
with t
Bjorn Stabell reported:
> http://linuxfab.cx/indexNewsData.php?NEWSID=2949&FIRSTHIT=1
>
> 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
http://linuxfab.cx/indexNewsData.php?NEWSID=2949&FIRSTHIT=1
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 organizati
I believe that result is incorrect. The
RACE has 48 bytes, so 44 bytes of Base32. That translates to 44 * 5 bits =
220 bits, or 27 bytes of compressed UTF-16. That must represent *at least* 13
UTF-16 characters, but the enclosed file only has 5 Hangul Syllables. If that
was generated program
Please let's keep types for single characters and types for strings separate.
ICU used to be in the same situation as Java: everything character/string used 16-bit
types.
In extension to UTF-16, we decided to keep the string base type at 16 bits for very
good reasons like interoperability and m
Dear Chris Fynn,
This font should be tried without Uniscribe support and without any other
fully conformant Tamil fonts to understand the scientific principles behind
the current recommendations. Of course in real use these supports are
essential. I'll soon be publishing the new version font f
John O'Conner wrote:
> Yes. If you have been involved with Unicode for any period of time at all, you
> would know that the Unicode consortium has advertised Unicode's 16-bit
> encoding for a long, long time, even in its latest Unicode 3.0 spec. The
> Unicode 3.0 spec clearly favors the 16-bit en
Dear All,
Some time ago, there was a discussion here about the Persian decimal
separator. I am posting a short report about our queries into different
Iranian bodies. Sorry for the long and somehow formal thing, but it seems
important to us.
I'm still waiting for responses from Iranian Academy
Jungshik Shin wrote:
> That's exactly what I have in mind about Java. I can't help wondering why
> Sun chose 2byte char instead of 4byte char when it was plainly obvious
> that 2byte wouldn't be enough in the very near future. The same can be
> said of Mozilla which internally uses BMP-only as
>>> On Wed, 2000 Nov 15 05:18:24 -0800 (GMT-0800) nikita k
>>> <[EMAIL PROTECTED]> wrote:
>>> Is there any text editor by which data can be entered
>>> in Hindi?
>>>
>>> Rgds,
>>> Nikita K
You could use Nisus Writer. However, we currently have an
unsolved bug in our support of Hindi, as the inse
On Wednesday, November 15, 2000, at 12:08 PM, Roozbeh Pournader wrote:
>
>
> On Wed, 15 Nov 2000, Michael (michka) Kaplan wrote:
>
> > I do not think they are so theoretical, with both 10646 and Unicode
> > including them in the very new future (unless you count it as
> theoretical
> > when
The Soviet language policies under both Lenin and Stalin were amazing in
what they managed to change in a very short time, especially considering the
scripts first shifted from Arabic to Latin, then just a decade or so later
to Cyrillic. I too have been wondering when there would be a movement in
On Wed, 15 Nov 2000, Thomas Chan wrote:
> On Wed, 15 Nov 2000, Jungshik Shin wrote:
>
> > On Wed, 15 Nov 2000, Michael (michka) Kaplan wrote:
> > >
> > > Many people try to compare this to DBCS, but it really is not the same
> > > thing understanding lead bytes and trail bytes in DBCS is *a
On Wed, 15 Nov 2000, Michael (michka) Kaplan wrote:
> I do not think they are so theoretical, with both 10646 and Unicode
> including them in the very new future (unless you count it as theoretical
> when you drop an egg but it has not yet hit the ground!).
Lemme think. You're saying that when
Hello,
A similar question to the question of new Chinese characters and new versions of
characters for Lakota, but an order of magnitude larger, is the question of ongoing or
about-to-hit-us script changes in Central Asia.
In the 1920s-1940s, under a series of Soviet language policy changes
On Wed, 15 Nov 2000, Jungshik Shin wrote:
> On Wed, 15 Nov 2000, Michael (michka) Kaplan wrote:
> > In any case, I think that UTF-16 is the answer here.
> >
> > Many people try to compare this to DBCS, but it really is not the same
> > thing understanding lead bytes and trail bytes in DBCS i
> From: Rick McGowan [mailto:[EMAIL PROTECTED]]
>
> Mike Ayers wrote:
>
> > The last I knew,
> > computer-savvy Taiwan and Hong Kong were continuing to invent new
> > characters. In the end, the onus is on the computer to
> support the user.
>
> Yes, the computer should support the user, but...
David Tooke wrote:
>
> Does anyone know of a freely available font with Unicode encodings containing
>characters in
> the Sinhala range (0D80-0DFF)?
" freely available " ... Challenging question, for sure.
> I can find several fonts with the character set, but none with Unicode encodings...
On Wed, 15 Nov 2000, Doug Ewell wrote:
> Elliotte Rusty Harold <[EMAIL PROTECTED]> wrote:
>
> > There are a number of possibilities that don't break backwards
> > compatibility (making trans-BMP characters require two chars rather
> > than one, defining a new wchar primitive data type that is
On Wed, 15 Nov 2000, Michael (michka) Kaplan wrote:
> In any case, I think that UTF-16 is the answer here.
>
> Many people try to compare this to DBCS, but it really is not the same
> thing understanding lead bytes and trail bytes in DBCS is *astoundingly*
> more complicated than handling su
Eliotte Rusty Harold wrote:
> One thing I'm very curious about going forward: Right now character
> values greater than 65535 are purely theoretical. However this will
> change. It seems to me that handling these characters properly is
> going to require redefining the char data type from two
Does anyone know of a freely available font with
Unicode encodings containing characters in the Sinhala range
(0D80-0DFF)?
I can find several fonts with the character set,
but none with Unicode encodings...they seem to map to the Latin range
instead.
Thanks in advance.
David Tooke
Elliotte Rusty Harold <[EMAIL PROTECTED]> wrote:
> There are a number of possibilities that don't break backwards
> compatibility (making trans-BMP characters require two chars rather
> than one, defining a new wchar primitive data type that is 4-bytes
> long as well as the old 2-byte char typ
I do not think they are so theoretical, with both 10646 and Unicode
including them in the very new future (unless you count it as theoretical
when you drop an egg but it has not yet hit the ground!).
In any case, I think that UTF-16 is the answer here.
Many people try to compare this to DBCS, bu
Wednesday, November 14, 2000
Oh I see the long right leg is straight. Sorry.
Regards,
Jim Agenbroad ( [EMAIL PROTECTED] )
The above are purely personal opinions, not necessarily the official
views of any government or any agency of any
On Tue, 14 Nov 2000, Rick McGowan wrote:
> [EMAIL PROTECTED] wrote:
>
> > Unfortunately, there's no corresponding LATIN CAPITAL LETTER N WITH LONG
> > RIGHT LEG, which Lakota needs.
>
> To my knowledge, the discussion in September between John Cowan and Curtis
> Clark didn't terminate with any
One thing I'm very curious about going forward: Right now character
values greater than 65535 are purely theoretical. However this will
change. It seems to me that handling these characters properly is
going to require redefining the char data type from two bytes to
four. This is a major incom
Hi,
Is there any text editor by which data can be entered
in Hindi?
Rgds,
Nikita K
__
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/
I just made some fixes in my Javascript Unicode
pages (insomnia again) that may be of interest.
http://www.macchiato.com/unicode/convert.html has
UTF, RACE and LACE conversions, with a bit better error checking.
http://www.macchiato.com/unicode/charts.html has
Unicode charts, plus a new "
31 matches
Mail list logo
