On 08/19/2013 03:21 PM, Darryl L. Pierce wrote:
On Fri, Aug 16, 2013 at 01:55:15PM +0100, Gordon Sim wrote:
On 08/16/2013 01:15 PM, Darryl L. Pierce wrote:
I reverted my changes, and would like to collaborate with you on a
better, more considered solution to the problem of sending properties
>from Perl and the other dynamic languages.
For Perl, what was wrong with the original code (as it is now you
have reverted your changes)? It looks like that allows one to
explicitly pass utf8 strings that will then be encoded as such.
Whats the problem statement?
The fundamental issue is that, regardless of the dynamic language,
properties aren't being encoded as UTF-8 at all.
Even if, in Perl, they are being set as UTF8? Are you saying that the
existing test in the Perl bindings doesn't work (i.e. doesn't actually
allow you to chose between utf8 or binary)?
For python, might one solution be to encode unicode strings as utf8?
Again that at least gives you the ability to control what happens.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
