Updates! On Wed, Aug 15, 2012 at 12:16 AM, Andrey Somov <py4...@gmail.com> wrote: > http://jira.codehaus.org/browse/JRUBY-6317 > > (http://code.google.com/p/snakeyaml/issues/detail?id=147)
This issue was fixed already for 1.11, but appears to have been on hold because we were not responsive on other issues. Hopefully it can move forward now. > http://code.google.com/p/snakeyaml/issues/detail?id=146 This one has a patch provided (by me) that appears to work and passes all tests. It was held up because py4fun asked for clarification about when it happens and I never updated. > http://code.google.com/p/snakeyaml/issues/detail?id=132 I recommended this one to be closed, since I believe the Ruby YAML "psych" implementation is evolving to fit SnakeYAML a bit better. We can deal with it in the future. Note that the JRuby issue related to this was closed some time ago, but I guess we forgot to update the SnakeYAML issue. Also: http://code.google.com/p/snakeyaml/issues/detail?id=158 I have provided a working patch here. This patch fixes these issues and introduces no failures: * All unprintable characters should be encoded all the time (YAML spec). * 32-bit unprintable characters should be encoded using \UXXXXXXXX instead of \uXXXX\uXXXX. So that makes one issue you fixed, two I fixed, and another that isn't important anymore. Can 1.11 move forward with that? What can I do to help? I believe there's only one failure if we update to 1.11 from SnakeYAML head right now, and it looks minor (i.e. maybe ignorable). Sorry again for delays in getting back to you! Crazy summer! - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
