Why does IOS client code use isoLatin1?

[kkwd]

Why does IOS client code use isoLatin1?

[nuclearace]

What? The client doesn't use isoLatin1, it uses unicode. And the latest version of the client only works with socket.io 2.0, since the way that unicode was encoding changed between 1 and 2.

[kkwd]

The ISO terminal is a small end encoding.

[nuclearace]

Once strings get to you, they should be standard Swift strings, which are fully unicode compatible. What issues are you seeing?

[kkwd]

Android and Web Chinese normal, IOS client Chinese garbled, server UTF-8

[nuclearace]

What server version? The current version of the client only supports socket.io 2.0. If your server is 1.0 you will see garbled unicode, since there was a breaking change between 1 and 2.

[lianxiang1]

hi I have the same problem @nuclearace
`//NSData *jsonData = [jsonString dataUsingEncoding:NSUTF8StringEncoding];

NSData *jsonData = [jsonString dataUsingEncoding:NSISOLatin1StringEncoding];`

When I use NSUTF8StringEncoding to parse callback data ，Chinese is messy code. but ,use NSISOLatin1StringEncoding is right.

[nuclearace]

@lianxiang1 What server version? See my above post.

[kkwd]

Other project versions of server 1.7.16 https://github.com/mrniko/netty-socketio

[nuclearace]

Looks like that only supports socket.io 1.0, so the current version of the client will not work with it, you'll see your issue. You'll have to use the 1.0 branch. Note that it's no longer supported however.

[nuclearace]

Looks like there's an issue on that project about it. mrniko/netty-socketio#566

[nuclearace]

Also just an FYI, this client is only built for the reference implementation of socket.io, which is the node based socket.io. It's up to other vendors to respect the socket.io protocol.

[kkwd]

Thank you