YAML doesn't do any special treatment of characters above 0xFF;  it assumes all valid Unicode code points above 0xFF are non-break-non-white "printable" characters and allows them to be used most anywhere.

We used to treat NEL, LS, PS as line breaks but we gave it up to maintain JSON compatibility. We are OK as long as YAML is a superset of JSON, which seems to be the case.

Oren.

On Thu, Aug 9, 2012 at 2:18 AM, Trans <transfire@gmail.com> wrote:
---------- Forwarded message ----------
From: Brendan Eich <brendan@mozilla.org>
Date: Wed, Aug 8, 2012 at 2:17 PM
Subject: Re: Hash style comments
To: Russell Leggett <russell.leggett@gmail.com>
Cc: es-discuss@mozilla.org


Pedantry alert: someone noticed that JSON does not treat U+2028 and
U+2029 (line terminators in JS) as space characters. So these can
occur (unescaped) in JSON string literals, but not in JS string
literals. Therefore JSON accepts sentences not legal in JS:

js> JSON.parse('{"a":"\u2028","b":2}')
({a:"\u2028", b:2})
js> eval('({"a":"\u2028","b":2})')
typein:11: SyntaxError: unterminated string literal:
typein:11: ({"a":"(
typein:11: ......^

Does YAML treat U+2028 and U+2029 the same as JSON does, or as JS does?

/be

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Yaml-core mailing list
Yaml-core@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yaml-core