4 ms·
No, Unicode text is not broken. It’s either your program that’s broken, for it is interpreting ISO-8859-X/Windows-12XX/whatever as UTF-X; or the program that pr
by tzahola 9y ago
No, Unicode text is not broken. It’s either your program that’s broken, for it is interpreting ISO-8859-X/Windows-12XX/whatever as UTF-X; or the program that produced said data.
- rspeer 9y agoI wrote the original library. Your statement is true, but in many cases, not useful. As quoted from the documentation [1]: > Of course you're better off if your input is decoded properly and has no glitches. But you often don't have any control over your input; it's someone else's mistake, but it's your problem now. [1] https://github.com/LuminosoInsight/python-ftfy https://github.com/LuminosoInsight/python-ftfy
- drinchev 9y agoThat's what I think as well. My native is Bulgarian and I've been through the whole range, you mentioned. What saves me is having File -> Open with Encoding ( Sublime Text ). Unfortunately they removed it from Chrome [1]. https://superuser.com/questions/1160003/how-do-i-change-the-character-encoding-for-a-webpage-in-chrome https://superuser.com/questions/1160003/how-do-i-change-the-...