Felix -- > I've opened issue 4832 last week with the intent to add support for > non-UTF8 encodings to PSON. > I consider PSON to be quite desirable, but the hardcoding to UTF8 is a > show stopper for us.
I've looked at the ticket and have a slightly different take on the issue. We've moved _away_ from iconv due to portability issues, and should not be passing un-escaped binary data in the PSON stream. Just turning off support for unicode isn't going to give support for having un-escaped binary data; unicode collisions are just one of the possible failure modes. Do you have an objection to UTF8 beyond the problem with un-escaped non-UTF-8 data, or is that the core of what makes it a show stopper? -- 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.
