Re: UCN (Java) notation beyond the BMP

From: addison@inter-locale.com
Date: Wed May 23 2001 - 17:49:02 EDT


I miswrote when I said "infrastructure"... there is clearly infrastructure
to support the characters and for "valid" pairs (that is a low surrogate
paired with a high surrogate being "one character"), but that's it. And
that's as good as, say, Win2K can do at this point.

The problem, of course, is that Java has no real way of referring to a
high-plane character itself or of getting the character properties (let
alone things like casing). That has to wait for 1.4, AFAIK. So a lot goes
into one's definition of "support"

Addison

===============================================================
Addison P. Phillips Globalization Architect
webMethods, Inc http://www.webmethods.com
Sunnyvale, CA, USA mailto:aphillips@webmethods.com

+1 408.210.3569 (mobile) +1 408.962.5487 (ofc)
===============================================================
"Internationalization is not a feature. It is an architecture."

On Tue, 22 May 2001, Michael (michka) Kaplan wrote:

> From: <addison@inter-locale.com>
>
> > (JDK 1.4 will only add
> > support for Unicode 3.0, not 3.1, although presumably it will add the
> > infrastructure for surrogate pairs which will allow your question to get
> > answered meaningfully!)
>
> Actually, no proper support for surrogate pairs means no support for
> *UNICODE 2.0*, let alone 3.0 or 3.1. Thats when the mechanism was added, and
> I think it is a bit more then pedantic to make sure a correction. :-)
>
> MichKa
>
> Michael Kaplan
> Trigeminal Software, Inc.
> http://www.trigeminal.com/
>
>
>



This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:18:17 EDT