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


--- Comment #22 from Jirka Kosek <jirka@kosek.cz> ---
(In reply to Anne from comment #19)
> I've seen sites rely on it for iso-8859-1. No doubt that's the case for
> us-ascii too. 

Do you have any evidence of us-ascii used there? I would be very surprised to
find such examples. In 90' iso-8859-1 was default. But if you characters were
not available in iso-8859-1 then other single-byte encodings were used. In my
country there were something like 5 different encoding used depending on
browser and operating system used and then you have to find way how to handle
this encoding mess. But there were no reason to change anything if iso-8859-1
was superset of characters you needed.

So rather then relying on speculations than 20 years ago us-ascii was used in
some strange way I would prefer having its definition reflect how it works in
many existing implementations and libraries.

Anyway encoding spec is now in the Last Call and since you reverted my previous
reopening of this bug, I suggest that you reopen bug yourself to give it proper
LC handling and consideration.

Thanks, Jirka

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

Received on Sunday, 29 June 2014 16:05:59 UTC