Possible encoding issue

[precipice]

I made a comment during a move on an in-progress game. The comment started:

No—I ... (and then there was more of the comment)

My opponent replied (as seen on DGS' site):

the beginning of your last post was: No—I

In the DGS app, his comment reads:

the beginning of your last post was: No—I (and no more of the comment came through for him)

Generally looks like a comment encoding issue to me; I'll take a look at this in a bit.

[precipice]

Oh, interestingly, if I look at the comment history on DGS's site, the full comment made it through, just with a weird formatting of the em-dash, which apparently causes the DGS app to truncate the comment.

[justinweiss]

Yep, that's usually a double-encoding issue - You send UTF-8, it's parsed as Windows-1252, and then re-encoded to UTF-8.

Funny enough, I wrote about this category of problems a little while ago: https://www.justinweiss.com/articles/how-to-get-from-theyre-to-theyre/

[precipice]

I'm seeing this again with the current build, on iOS 11.1, iPhone X, Dragon Go Client 2.1. The issue appears to be "smart" apostrophes. They're rendered on dragongoserver.net as ’ (e.g., in It’s). I'll take a look to see if I can find the problem.

[justinweiss]

Hm, interesting. Encoding has been a huge issue because of all of the different languages DGS supports, and I haven't been able to find a way to handle them that's totally consistent.