« Chupei #3: JSON::Syck and YAML.pm released. | Main | lighttpd++ »

2006.01.11

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83451e8fb69e200d834a69a0d69e2

Listed below are links to weblogs that reference A bit more YAML::Syck.:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Man. You are a syck!

(In the good way)

-ben

The Syck repository is open for all (you have to have a Rubyforge account as a prerequisite):

 http://code.whytheluckystiff.net/svn/syck/trunk

I've sort of glanced through perl_syck.h. How nice that Perl has a pile of UTF-8 calls.

a dumb question...

YAML::Syck munges Unicode text into \xHH format, whilst YAML doesn't.

i understand that this is a limitation of libsyck itself. but how do i convert the munged text back into native Unicode?

Set $YAML::Syck::ImplicitUnicode to a true value.

Also, if your Unicode text is properly marked as such (via utf8::decode or Encode::decode or the :encoding or :utf8 input layer), then it should serialize without escaping.

It's arguably broken if YAML.pm serializes unmarked byte strings into unescaped UTF-8.

Nevertheless, it would be nice, if you can find some time to send it back to Why.

Why is aware of my UTF8 treatment and we've discussed it on #perl6 a while ago. :-) (Hi stas!)

The comments to this entry are closed.

June 2014

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          

Audrey

My Photo

License