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


--- Comment #37 from Jirka Kosek <jirka@kosek.cz> ---
(In reply to Henri Sivonen from comment #36)
> (In reply to Jirka Kosek from comment #18)
> > I agree that all should agree on how encodings works, but it seems that in
> > this quest for unification everything except browsers is ignored.
> I think the Encoding Standard should describe the required behavior for
> implementations of the Web Platform--i.e. browser engines. 

Then this should be clearly articulated in the scope of the Encoding Standard.
Current wording and responses from Anne indicate that intention of the Encoding
Standard is to cover entire universe.

> Other software
> that wants to be Web-compatible is welcome to implement the spec, too.
> However, I think it would be wrong to change the spec and browser
> implementations to make pre-existing non-browser behaviors "correct" per
> spec.

So far no one showen where browsers implement us-ascii as an windows-1252 alias
for *encoding*, so to me it seems that change I propose (replace or escape
characters above U+007F for us-ascii encoding) doesn't change anything in
browser implementations.

> (In reply to Jirka Kosek from comment #9)
> > Consider the following example. I have page containing copyright symbol
> > (U+00A9). I want to save it in "us-ascii" encoding using XHTML syntax of
> > HTML5.
> You want something that's hostile to interop, then. The spec should not
> accommodate what you want.
> In other words, the right solution is to always use UTF-8 when you create
> XML documents. 

In ideal world yes, but when you have other constraints and you know that
receiver can handle us-ascii then why it should be broken?

Also same could be applied to any other text based format then XML. XML was
only example that easily shown error using widely deployed libraries.

> I request this Bugzilla item be WONTFIXed.

I would rather see if browser vendors can prove that changing the current
definition of us-ascii encoding breaks anything. Please note that the Encoding
Standard changes how us-ascii encoding behaved in the past, so this change must
be justified and well reasoned. Not vice versa.

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

Received on Tuesday, 1 July 2014 09:57:25 UTC