Re: [protobuf] Python and Java: different byte sequences and tag errors

2014-05-24 Thread Alessandro Sivieri
On Saturday, May 24, 2014 2:29:57 AM UTC+2, Oliver wrote:
>
> In fact looking at the exact data this is almost certain to be what's 
> happening. Bytes >128 are being replaced by the three byte sequence 0xef 
> 0xbf 0xbd which is the UTF-8 encoding of U+FFFD - the "replacement 
> character" often used to replace unrepresentable characters when 
> transcoding.
>
>
Ok, then I probably know what is causing the problem, and it is exactly the 
fact that the byte sequence is then being represented as a string. I need 
to better check the ZeroMQ API and see what I can do about it.

Thanks for your help! 

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.


Re: [protobuf] Python and Java: different byte sequences and tag errors

2014-05-23 Thread Oliver Jowett
On 24 May 2014 01:23, Oliver Jowett  wrote:

> On 23 May 2014 22:06, Alessandro Sivieri wrote:
>
>>
>>
> I don't think the communication channel is causing any problem, because
>> the array sequences are not simply truncated but really different (I would
>> expect them to be identical).
>>
>
> Check again; it looks like your Java path is mangling (only) bytes >128.
> Perhaps this path tries to interpret the byte sequence as a string, and
> charset transcoding mangles your data?
>

In fact looking at the exact data this is almost certain to be what's
happening. Bytes >128 are being replaced by the three byte sequence 0xef
0xbf 0xbd which is the UTF-8 encoding of U+FFFD - the "replacement
character" often used to replace unrepresentable characters when
transcoding.

Oliver

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.


Re: [protobuf] Python and Java: different byte sequences and tag errors

2014-05-23 Thread Oliver Jowett
On 23 May 2014 22:06, Alessandro Sivieri wrote:

>
>
I don't think the communication channel is causing any problem, because the
> array sequences are not simply truncated but really different (I would
> expect them to be identical).
>

Check again; it looks like your Java path is mangling (only) bytes >128.
Perhaps this path tries to interpret the byte sequence as a string, and
charset transcoding mangles your data?

Oliver

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.