On 09/29/2010 04:45 PM, Markus Roberts wrote: > ... > 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?
Hi Markus, yes, we're not trying to serialize arbitrary binary data. But we do want to have files with content in German, including umlauts. It might be acceptable to convert all our files to UTF8, but puppet would be our sole reason for it, which doesn't sit quite right with me. What do you mean by "unescaped"? Can non-ASCII symbols be escaped in any way in non-UTF encoded text? Even if that was the case, I guess we might as well go ahead and convert the manifests and templates to UTF8, instead of messing with our Latin1 texts. Regards, Felix -- 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.
