[Bug 23646] "us-ascii" should not be an alias for "windows-1252"

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23646

--- Comment #29 from Jirka Kosek <jirka@kosek.cz> ---
(In reply to Anne from comment #25)
> Jirka, the evidence I have is that the most widely deployed software
> exhibits this behavior. Unless that changes, I don't see a reason to change
> this document.

Anne, could you please show me browser function which deals with text encoding
and which treats us-ascii same way as windows-1252? So far, I haven't seen
this, but I have provided several examples where treating us-ascii as alias for
windows-1252 create interop problems.

Please note that I'm fine with treating us-ascii as windows-1252 for purposes
of decoding.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 1 July 2014 07:12:26 UTC