On Wed, Dec 9, 2009 at 11:06 AM, Burt Harris <Burt.Harris@...:
> Yaml 1.2 removed 1.1’s the special treatment of three non-ASCII line
> break characters. I’m updating my code & tests to match.
> This has broken several unit tests based on examples from the 1.1
> specification which included these. That’s expected, right?
> The intent is that a 1.2 compliant implementation should _*not*_ consider
> these as line breaks, particularly for the purposes of calculating
> indentation, right?
Yes. This is due to the fact that JSON does not consider these to be line
breaks. To make YAML to be a superset of JSON, we had no choice but to make
this change. We figured that this shouldn't affect (most) every files out
there in the world.
> In example 8.5 of the 1.2 spec, a double down arrow glyph used in the 1.1
> spec to represent line separators \x2028 still appears. I’m guessing
> that’s a typo, since when I replace it with a generic line break, I get the
> expected output. **
Yes. Thanks for catching this.