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


--- Comment #17 from Jirka Kosek <jirka@kosek.cz> ---
(In reply to Anne from comment #16)
> (In reply to Jirka Kosek from comment #15)
> > Is there any real reason why *encoding* when "us-ascii" is used for HTML
> > can't be changed?
> Web content.

Please be specific. There is surely existing content that relies on *decoding*
"us-ascii" as "windows-1252". But where is such content or applications that
rely on this for *encoding*?

> > It's usually when you are using non-HTML/XML content that you need to use
> > non-UTF encodings and then you must be much more picky about how encoders
> > work. So if spec should be bended some way then to cater for such cases.
> Why would that be true? <form> submission and URL query parameter encoding
> are a thing and given the scale of the web they are widespread.

Is "us-ascii" used there?

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

Received on Saturday, 28 June 2014 11:36:17 UTC