Three spec failures related to YAML in ruby 2.0 about twitter-cldr-rb

[camertron]

Ugh yeah, we see these on JRuby too. I've spelunked through the code a few times looking for the bug with no success. I'm pretty sure this is related to the different YAML parsers that various versions of Ruby come with. MRI 1.8 comes with Syck, which parses UTF-8 correctly. MRI 1.9 comes with Syck, which still works, and Psych, which doesn't. MRI 2.0 comes with only Psych, which explains the errors you're seeing.

There's a syck gem available that re-introduces the YAML engine manager, but I'd rather not depend on it considering that Psych is the way forward. It looks like there are a few issues filed against Psych that might help, and it makes sense to run TwitterCLDR's YAML tests against the pre-release of MRI 2.1 to see if our particular issues have been addressed. Short of going on another deep-dive into the YAML dumper, Psych, and libyaml, that's all I can suggest :(

[jrochkind]

Do you think it's likely safe to run the gem on ruby 2.0, ignoring those failed tests?

Am I right that the goal of your yaml fixes is just making yaml files containing unicode easier for humans to read and write? I wonder if it makes sense to just abandon this, and either get your fixes into Psych upstream, or give up on having em. But just an idea, I haven't personally encountered much of the pain your custom yaml fixes are meant to ameliorate.

[camertron]

Yes, the goal of these fixes is to make yaml with unicode dump correctly so it doesn't get loaded as a jumble of unrecognizable characters (which also has the side effect of being easier to read in the yaml files themselves). Since I don't have time to look into these failures now, I'd say let's just ignore them. As I said before, unicode-safe yaml dumping is really meant to help people using MRI 1.8, and since that (still) works, I'd say let's not worry too much about the failures.

[camertron]

I went ahead and "fixed" these failures (pretty hacky, but c'est la vie). Everything should be passing in the v3.0 branch.