On 19/11/2009, at 21:21, Kovalevski Andrei wrote:
> Hi,
>
> the string is ok, but the problem is inside the message. The length of the
> message is incorrect:
>
> your message:
> 510046557064617465207472616E73616374696F6E7320736574206465736372697074696F6E3D27546573742056616C75657364C387272
Hi,
the string is ok, but the problem is inside the message. The length of
the message is incorrect:
your message:
5100*46*557064617465207472616E73616374696F6E7320736574206465736372697074696F6E3D27546573742056616C75657364C387272077686572652069643D313133
it should be:
5100*45*5570646
On 19/11/2009, at 18:13, Raimon Fernandez wrote:
>
> On 19/11/2009, at 17:27, Kovalevski Andrei wrote:
>
>> Hi
>>
>> could it be that you have errors in your UTF8 string? For example you might
>> use UTF16 encoding, it can explain why some characters force errors but
>> others are not.
>
>
On 19/11/2009, at 17:27, Kovalevski Andrei wrote:
> Hi
>
> could it be that you have errors in your UTF8 string? For example you might
> use UTF16 encoding, it can explain why some characters force errors but
> others are not.
It only happens with values like àéïçñ I think UTF8 can handle thi
Hi
could it be that you have errors in your UTF8 string? For example you
might use UTF16 encoding, it can explain why some characters force
errors but others are not. Can you post here the string and its' encoded
version?
Raimon Fernandez wrote:
Hello,
I'm trying to send some strings that
Hello,
I'm trying to send some strings that have chars outside from standar ascii,
like çñàèó
Once I'm connected, the client and server both uses UT8Encoding.
And I'm sending all the strings encoded in UTF8.
At least the received ones are working, as I get the text exactly as it is,
with spe
