On Sat, 15 Oct 2011, Jukka K. Korpela wrote: > The reason is that by the HTML5 drafts, browsers are required > to treat iso-8859-1 as windows-1252. > From a different perspective, this is just madness – kludgy error > recovery turned to a standard and an international, widely deployed > standard flushed down the toilet in favor of a vendor-specific encoding. Right. And one may ask: Why not do the same for ISO-8859-9 and Windows-1254, for ISO-8859-11 and Windows-874? Or why not treat *all* 8-bit encodings as Windows-1256?Received on Saturday, 15 October 2011 15:03:34 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:59:23 UTC