3 ms·
A simpler test FWIW.. type: data:text/html,<html> Into your url bar and inspect that. Avoids server messing with encoding values. And yes, here on my lin
by capitainenemo 3y ago
A simpler test FWIW..
type:
data:text/html,<html>
Into your url bar and inspect that. Avoids server messing with encoding values. And yes, here on my linux machine in firefox it is windows-1252 too.
(You can type the complete document, but <html> is sufficient. Browsers autocomplete a valid document. BTW, data:text/html,<html contenteditable> is something I use quite a lot)
But yeah, I think windows-1252 is standard for quirks mode, for historical reasons.
- layer8 3y agoThe historical (and present?) default is to use the local character set, which on US Windows is Windows-1252, but for example on Japanese Windows is Shift-JIS. The expectation is that users will tend to view web pages from their region.
- kalleboo 3y agoI'm in Japan on a Mac with the OS language set to Japanese. Safari gives me Shift_JIS, but Chrome and Firefox give me windows-1252 edit: Trying data:text/html,<html>日本語 makes Chrome also use Shift_JIS, resulting in mojibake as it's actually UTF-8. Firefox shows a warning about it guessing the character set, and then it chooses windows-1252 and displays more garbage.
- slt2021 3y ago>data:text/html,<html contenteditable> thank you, I learned nice trick today. re windows1252 - this could be driven by system encoding settings, for most people it is 1252, but for eastern europe it is windows-1251. when viewed from IBM z mainframe - encoding will be something like IBM EBCDIC
- capitainenemo 3y agoWell, I'm on Linux - system encoding set to UTF-8 which is pretty much standard there. But I think the "windows-1252 for quirks" is just driven by what was dominant back when the majority of quirky HTML was generated decades ago.