Tweet with broken encoding causes issues with TextAsHtml and serializing as XML complains about about tweetmoasharp HOT 5 CLOSED

Hi,

Thanks for the problem report :)

I've spent some time looking and I think the problem is the TextAsHtml function. I believe the twitter entity indices are true 'character' positions, but the string/stringbuilder methods used to parse and update the original string are really byte based (regardless of what the docs might say). I've seen/suspected this before but never found a solution.

In your sample tweet the first url entity has a start index of 106, but the string functions being used only return the correct text if position 110 is used. The additional 4 bytes seem to be because each of the emoji/smiley characters is actually 2 bytes but being treated as 1. I think this can be solved using System.Globalization.StringInfo to measure actual characters, but I've run out of time tonight to try and produce a solution.

from tweetmoasharp.

Hi,

I think I may have fixed the problem. I've pushed a new build to nuget, could you please update your solution and try again to see if this helps?

Thanks.

from tweetmoasharp.

Hi,

Any chance you've tried the update? Can I close this issue?

Thanks.

from tweetmoasharp.

Thanks for your speedy response! This indeed fixes the issue so it can be closed. Thanks again.

from tweetmoasharp.

👍 Thank you!

from tweetmoasharp.