[webkit-dev] HTML5 & Web Links (RFC 5988)
julian.reschke at gmx.de
Sat Feb 12 05:13:46 PST 2011
On 12.11.2010 09:29, Julian Reschke wrote:
>> Surely, there is no way (that I'm aware of) to guarantee correct
>> downloaded file name in all browsers for all users. A lot of server
>> operators only care about users in their country, and can reasonably
>> (i.e. with negligible cost to business) rely on Windows locale being
>> set. They can just send raw bytes in language default encoding in
>> Content-Disposition, and that works for them and their clients. For
>> all I know, that's what almost everyone does, and it's "interoperable"
>> for them.
> Yes. That was the case back in 2003 when I only had to worry about IE
> and Mozilla/Firefox, and it hasn't been improving until 2008 when I
> started the work on collection test cases *and* results, and started
> updating the specs.
> Since then some of the implementations of 2231 encoding (now 5987) have
> improved a bit (Opera) / a lot (Konqueror), FF has a few pending
> patches, and Chrome nighties have started implementing this (two weeks
> So we are making slow progress now.
Just for the record: Chrome 9 with 2231/5987 is released. Furthermore,
IE9RC supports the 2231/5987 encoding (UTF-8 only). So Safari is the
last UA left not supporting this.
Best regards, Julian
More information about the webkit-dev