Re: PDUTR #27: Unicode 3.1

2001-01-24 Thread Yung-Fong Tang
The Unicode case mapping in Mozilla implementation is pretty compact and open source. The whole case mappint table only take 1.2 K of memory. Read http://people.netscape.com/ftang/paper/unicode17/case/ for details. Markus Scherer wrote: ICU stores most UnicodeData.txt properties in its

RE: PDUTR #27: Unicode 3.1

2001-01-23 Thread Peter_Constable
On 01/22/2001 01:11:42 PM Kenneth Whistler wrote: I agree that Mark Davis' discussion covers many of the tricks to make things small *and* fast when dealing with Unicode tables. However, you can start out with relatively simple approaches and still get excellent performance in both memory and

Re: PDUTR #27: Unicode 3.1

2001-01-23 Thread Markus Scherer
ICU stores most UnicodeData.txt properties in its uprops.dat, currently some 23kB (Unicode 3.0). This does not include character names, which are in unames.dat, currently some 83kB. There is currently a bug about wrong properties for the last 1k chars in plane 15 16 (I will try to fix this

Re: PDUTR #27: Unicode 3.1

2001-01-23 Thread Peter_Constable
Thanks for the info. Peter On 01/23/2001 12:56:45 PM Markus Scherer wrote: ICU stores most UnicodeData.txt properties in its uprops.dat, currently some 23kB (Unicode 3.0). This does not include character names, which are in unames.dat, currently some 83kB. There is currently a bug about

Re: PDUTR #27: Unicode 3.1

2001-01-22 Thread Peter_Constable
On 01/20/2001 03:05:23 AM "Mike Lischke" wrote: I had a quick look at it and got a question which you might be able to answer. Windows cannot display UTF 32 characters, AFAIK Linux does not either. So which common operating system can actually display UTF 32? It is true that there is no Win32

Re: FW: replay address (was: PDUTR #27: Unicode 3.1)

2001-01-22 Thread John Cowan
Mike Lischke wrote: PS: It seems that the that reply address in this mailing list is set to the original author instead the list itself. This is quite useless and requires manually edit of the target address when posting a reply. Could we please change the settings for this list so that the

Re: FW: replay address (was: PDUTR #27: Unicode 3.1)

2001-01-22 Thread Michael \(michka\) Kaplan
y 22, 2001 6:42 AM Subject: Re: FW: replay address (was: PDUTR #27: Unicode 3.1) Mike Lischke wrote: PS: It seems that the that reply address in this mailing list is set to the original author instead the list itself. This is quite useless and requires manually edit of the target ad

RE: PDUTR #27: Unicode 3.1

2001-01-22 Thread Peter_Constable
On 01/22/2001 10:28:42 AM Mike Lischke wrote: This is very interesting. How would you encode, say: 2F9EA;CJK COMPATIBILITY IDEOGRAPH-2F9EA;Lo;0;L;927CN; to UTF16? The workings of UTF16 are well known and clearly defined on p. 45, section 3.7 of TUS3.0, specifically in definition D28.

Re: PDUTR #27: Unicode 3.1

2001-01-22 Thread Mark Davis
ot;Unicode List" [EMAIL PROTECTED] Sent: Monday, January 22, 2001 07:51 Subject: Re: PDUTR #27: Unicode 3.1 On Sat, Jan 20, 2001 at 01:05:23AM -0800, Mike Lischke wrote: I had a quick look at it and got a question which you might be able to answer. Windows cannot display UTF 32 characte

Re: PDUTR #27: Unicode 3.1

2001-01-22 Thread David Starner
On Mon, Jan 22, 2001 at 05:35:24PM +0100, Mike Lischke wrote: Hi David, If by UTF-32 characters, you mean astral or non-BMP characters, recent (alpha) versions of xterm can display them. So this is an application specific feature, not from the operating system? Yes. But xterm

RE: PDUTR #27: Unicode 3.1

2001-01-22 Thread Kenneth Whistler
Peter Constable replied to an inquiry from Mike Lischke: I'm currently extending my Unicode library for Delphi and I wonder how to deal with all those new characters which are 64K? Particularly the character properties causing me headaches because of the memory requirements. Using a linear

RE: PDUTR #27: Unicode 3.1

2001-01-22 Thread Mike Lischke
Hi Peter, The workings of UTF16 are well known and clearly defined on p. 45, section 3.7 of TUS3.0, specifically in definition D28. (Available online at http://www.unicode.org/unicode/uni2book/ch03.pdf.) Excellent. I have recently downloaded the files but had not yet the opportunity to look

Re: PDUTR #27: Unicode 3.1

2001-01-20 Thread Mike Lischke
Proposed Draft Unicode Technical Report #27: Unicode 3.1 is now available at http://www.unicode.org/unicode/reports/tr27/ Please take a look at it and report any problems you may find. It is approximately 60 pages long. I had a quick look at it and got a question which you might be able

FW: replay address (was: PDUTR #27: Unicode 3.1)

2001-01-20 Thread Mike Lischke
-Original Message- From: R.C. Bakhuizen van den Brink [Rein] [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 20, 2001 12:03 PM To: Mike Lischke Subject: Re: PDUTR #27: Unicode 3.1 On Sat, 20 Jan 2001, Mike Lischke wrote: Mike Lischke RD Senior software engineer PS

PDUTR #27: Unicode 3.1

2001-01-17 Thread Julie Doll Allen
Proposed Draft Unicode Technical Report #27: Unicode 3.1 is now available at http://www.unicode.org/unicode/reports/tr27/ Please take a look at it and report any problems you may find. It is approximately 60 pages long. Julie Allen Editor, Unicode, Inc.