From: Mike Ayers (mike.ayers@tumbleweed.com)
Date: Tue Nov 23 2004 - 15:10:03 CST
> From: unicode-bounce@unicode.org
> [mailto:unicode-bounce@unicode.org] On Behalf Of Antoine Leca
> Sent: Tuesday, November 23, 2004 11:56 AM
> What is wrong? That UTF-8 (born FSS-UTF) was designed to be
> compatible with C language strings?'
Yes. A character encoding can be compatible with ASCII or C
language strings, but not both, as those two were not compatible to begin
with. UTF-8 was designed to be compatible with ASCII, or, more accurately,
"8 bit ASCII" (which is not a real standard but is better understood than
most standards). Because of this, C string handling of UTF-8 is
functionally and bug compatible with C string handling of ASCII, which is
what was intended to be said.
> > UTF-8 is fully compatible with ASCII,
>
> I do not know what does mean "fully compatible" in such a
> context.
As above, my bad. I meant that it is fully coimpatible with "8 bit
ASCII", 8 bit code in which the lower 128 code points are as defined in
ASCII, and the upper 128 code points are treated opaquely.
Hope that clarifies,
/|/|ike
"Tumbleweed E-mail Firewall <tumbleweed.com>" made the following
annotations on 11/23/04 13:13:02
------------------------------------------------------------------------------
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.
==============================================================================
This archive was generated by hypermail 2.1.5 : Tue Nov 23 2004 - 15:14:26 CST