-
Notifications
You must be signed in to change notification settings - Fork 84
Open
Description
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
› -> (UTF8) E2 80 BA
› -> (UTF16) 00E2 20AC 00BA
› -> 1110 0010 1000 0000 1011 1010
› -> 1110 0010 0010 0000 1010 1100 0000 0000 1011 1010
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,
Metadata
Metadata
Assignees
Labels
No labels