Re: Invalid UTF-8

On 8/28/09 1:56 PM, "William Spitzak" <[email protected]> wrote:

> Oren Ben-Kiki wrote:
> 
>> If I try to load them using a YAML
>> library that uses UTF-16 (e.g., a Java one), and the \X escape sequence
>> specifies an invalid UTF-8 byte sequence, then the library will be
>> forced to throw an exception. So the file is not "portable" to such a
>> system (cannot be loaded by it).

Hi,
I haven¹t had time to follow this discussion so I would like to make an
assertion and hope it¹s not refuted. XML made a serious mistake by asserting
that some bytes cannot be represented. It is illegal to say &#0; for the
justification that there is no uniform semantic for that entity. This
extends to other characters like &#12; (form feed), etc. This imposes a
burden on all XML users to attach an additional filtering layer and
separately and on a site-by-site basis establish things like ³&null;² or
³&formfeed;² when they want to communicate those bytes.

There should be no illegal bytes in YAML or perhaps better said, it must be
possible to represent all bytes in YAML.

Apologies for the Outlook client. I've tried to ensure this is plain text
and has line endings to keep the above paragraph from being a single line.

Josh


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july