4 ms·
Is this useful? Most Latin 1 text is really Windows 1252, which has additional characters that don't have the same regular mapping to unicode. So this conversio
by masfuerte 3y ago
Is this useful? Most Latin 1 text is really Windows 1252, which has additional characters that don't have the same regular mapping to unicode. So this conversion will mangle curly quotes and the Euro sign, among others.
- dotancohen 3y ago> Most Latin 1 text is really Windows 1252 I'd say that the vast majority of Latin-1 that I've encountered is just ASCII. Where have you seen Windows-1252 presented with a Latin-1 header or other encoding declaration that declared it as Latin-1?
- masfuerte 3y agoWindows 1252 served as Latin 1 used to be common enough that browsers interpret a Latin 1 declaration as Windows 1252. Nowadays it seems moderately common for such text to be served with a utf-8 declaration, so it gets mangled in other ways. Or it gets imported into a CMS with no conversion or the wrong conversion, which has a similar result. You're right, ASCII is more common, but single-byte encoded prose that goes beyond ASCII is usually Windows 1252 in my experience.
- dotancohen 3y ago> Windows 1252 served as Latin 1 used to be common enough that browsers > interpret a Latin 1 declaration as Windows 1252. Thank you, I had not encountered this and I was dealing a lot with improperly-encoded text when I was running gibberish.co.il (over a decade ago). What systems were serving this? IIS would be my first guess, an Intuit product would be my second.