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
ISO-8859-2 covers many of the same characters as Windows-1250, but unfortunately has the characters in different places.
An awkwardly ambiguous case that I've found is that the text SchlĂźsselwĂśrter gets decoded by ftfy as SchlßsselwÜrter, considering it to be Windows-1250 mojibake, when in fact it was ISO-8859-2 mojibake that should have said Schlüsselwörter. Distinguishing these without additional context would require recognizing the awkward capitalization and the extreme unlikeliness of the sequence "ßss".
The text was updated successfully, but these errors were encountered:
rspeer
changed the title
Feature: recognize ISO-8859-2 mojibake
Feature: distinguish ISO-8859-2 from windows-1250 mojibake
Feb 11, 2021
I previously made this note because I thought we weren't supporting ISO-8859-2 mojibake at all, but we are. This word decodes correctly in the context of other ISO-8859-2 mojibake.
ISO-8859-2 covers many of the same characters as Windows-1250, but unfortunately has the characters in different places.
An awkwardly ambiguous case that I've found is that the text
SchlĂźsselwĂśrter
gets decoded by ftfy asSchlßsselwÜrter
, considering it to be Windows-1250 mojibake, when in fact it was ISO-8859-2 mojibake that should have saidSchlüsselwörter
. Distinguishing these without additional context would require recognizing the awkward capitalization and the extreme unlikeliness of the sequence "ßss".The text was updated successfully, but these errors were encountered: