Re: YAML2

Devin Jeanpierre wrote:
>> There needs to be a way to put an arbitrary byte sequence into a scalar
>> without losing the ability to make valid byte sequences human-readable.
> 
> Mixing byte data into what is ostensibly unicode seems like a bad
> idea. Either have a particular part of the document be unicode, or
> bytes, not both.

As somebody else pointed out, my suggestion involves putting various 
combinations of the '\' and 'x' and 'u' and the hex digits into the 
file. All of these are valid Unicode.

That said, it would also be convenient for parsers to at least have a 
switch by which they will accept all non-ASCII bytes in a scaler 
absolutely unchanged. This will make it possible to read bad YAML files 
produced by programs that assumed all the input was valid UTF-8 and 
wrote it literally to the output file. This is a common problem with 
hand-editing when the character set is wrong so it should be supported. 
However I knew that would be controversial so I did not propose it as 
well. I am willing to patch YAML to a non-standard to support this.


------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World™ now supports Android™ Apps 
for the BlackBerry® PlayBook™. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev