Felix -- > What I don't really understand is how the serialization really works.
> If I read this right, each 16bit word (UTF16be encoded) is sent as > '\uXXXX' where XXXX is the hex representation? > So, "invalid" bytes should get a '/xXX' representation instead? (Without > attempting to convert to UTF16 of course) > Basically, yes. Part of this is handled by iconv which a) isn't supported on all platforms and b) doesn't work consistently on the platforms where it is. I think we may need to just write a pure ruby handler and be done with it, but haven't overcome the mental hurdle of "but we shouldn't have to do that!" -- M ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
