You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Again, not sure if › is causing the wrong charset detection / lures the algorithm since the binary isn't matching 1:1 but since 0x80 seems to be a special value in the algorithm I thought it could be an edge-case that could be fixed.
Cheers,
The text was updated successfully, but these errors were encountered:
Unsure if it can help but the character
›
was sometimes interpreted as›
on my website.Context
The charset was not specified properly in the html document (typo). No charset in the css file either where the char was used.
Data
Again, not sure if
›
is causing the wrong charset detection / lures the algorithm since the binary isn't matching 1:1 but since0x80
seems to be a special value in the algorithm I thought it could be an edge-case that could be fixed.Cheers,
The text was updated successfully, but these errors were encountered: