From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Douglas A. Gwyn" <DAGwyn@null.net>
Message-ID: <kPCcnX9rkoVKesKiXTWJhg@comcast.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
References: <adednXgYWfdPk8aiU-KYgw@comcast.com>, <00ec01c37784$cbe421e0$c901a8c0@cc77109e>
Subject: Re: [9fans] ... in the Kingdom of Sources
Date: Thu, 11 Sep 2003 09:07:30 +0000
Topicbox-Message-UUID: 30c64846-eacc-11e9-9e20-41e7f4b1d025

Bruce Ellis wrote:
> I guess I somehow missed what is hard about UTF-8 synchronization.

We weren't talking about a supposed problem with UTF-8,
but about a supposed problem with Standard C wide-character
facilities.  The Standard C facility has to deal with a
much wider variety of multibyte encodings.  In any event,
flagging a conversion error only by a specific value
embedded in the converted data means that the error will
be missed unless the application scans the data looking
for it.  Seems to me that encourages use of erroneous data.