OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java/Unicode brain damage

At 8:45 AM -0700 7/26/01, David Brownell wrote:

>Nah, people complain enough about wasted space ... admittedly
>there's a religous war on whether (in C terms) "wchar_t" should
>be 16 bits or 32.

Developers do waste time optimizing for space, I'll grant you, but nowadays people rarely complain because space optimization doesn't really matter anymore, certainly not for text. (Video, audio, and so forth is another issue, but not one that's relevant here.) Modern applications are incredibly profligate with memory, and for the most part nobody notices or cares. Memory and disk space is so cheap today, that the extra two bytes per character is insignificant.

For transmission and serialization, you can just use UTF-8, which would be identical to current usage as long as only BMP characters were used, and a tad more efficient than current practice for non-BMP characters.

| Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|              http://www.ibiblio.org/xml/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      | 
|  Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/     |