> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Addison Phillips [wM]
> Sent: Tuesday, November 23, 2004 9:14 AM
> One of the nice things about UTF-8 is that the ASCII bytes
> from 0 to 7F hex (including the C0 control characters from
> \x00 through \x01f---including NULL) represent the ASCII
> characters from 0 to 7F hex.
Correct.
> That is, amoung other things
> UTF-8 was designed specifically to be compatible with C
> language strings.
Wrong! Weren't you paying attention last week? C language strings are not even fully compatible with ASCII. UTF-8 is fully compatible with ASCII, therefore C language strings are not fully compatible with UTF-8. The Java folks devised a TES, which was UTF-8 with one change (and therefore no longer UTF-8), which was "designed specifically to be compatible with C language strings". This method apparently upsets some people.
Since the problem between C strings and ASCII/UTF-8/(your character set here) is solely the inability to handle zero valued character elements, it may be, and very often is, practical to use C strings anyway, as zero valued characters are uncommon at best in practice, and explicitly disallowed in many applications.
/|/|ike
"Tumbleweed E-mail Firewall <tumbleweed.com>" made the following
annotations on 11/23/04 10:34:18
------------------------------------------------------------------------------
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
==============================================================================
