W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2008

Re: [whatwg] Is EBCDIC support needed for not breaking the Web?

From: Henri Sivonen <hsivonen@iki.fi>
Date: Sun, 1 Jun 2008 18:00:58 +0300
Cc: "public-html@w3.org WG" <public-html@w3.org>, whatwg List <whatwg@whatwg.org>, public-i18n-core@w3.org, www-international@w3.org
Message-Id: <2D9C1549-5C1E-412A-9904-48F092589D6A@iki.fi>
To: Bjoern Hoehrmann <derhoermi@gmx.net>

On Jun 1, 2008, at 17:25, Bjoern Hoehrmann wrote:

> * Henri Sivonen wrote:
>> This makes me wonder: Do the top browsers support any EBCDIC-based
>> encodings but just without exposing them in the UI? If not, can there
>> be any notable EBCDIC-based Web content?
>
> Internet Explorer should support any character encoding Windows  
> supports
> (see the advanced tab in `control International`), which includes many
> EBCDIC encodings. See eg. http://www.websitedev.de/temp/ebcdic-cp-us.txt
> for an example.

Thanks.

Philip Taylor made a test case:
http://philip.html5.org/demos/charset/ebcdic/charsets.html

It shows that browsers that use general-purpose decoder libraries (IE  
and Safari) support some EBCDIC flavors but browsers that roll their  
own decoders (Firefox and Opera) don't.

Firefox and Opera being able get away with not supporting EBCDIC  
flavors suggests that EBCDIC-based encodings cannot be particularly  
Web-relevant. Even if saying that browsers MUST NOT support them might  
end up being a dead letter, it seems that it would be feasible to say  
that browsers SHOULD NOT support them or at least MUST NOT let a  
heuristic detector guess EBCDIC (for security reasons).

(Also, I think I'm going to remove EBCDIC support from Validator.nu.)

> It seems to me www-international@w3.org would have been
> a better place to ask your questions than the mailing lists you  
> picked.

So many lists. :-( CCed that one, too, just in case.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Sunday, 1 June 2008 15:01:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:55 GMT