W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2009

[whatwg] Worker feedback

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 29 Apr 2009 05:40:49 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0904290539030.12381@hixie.dreamhostps.com>
On Wed, 29 Apr 2009, Alexey Proskuryakov wrote:
> 29.04.2009, ? 6:05, Ian Hickson ???????(?):
> 
> > > Disregarding charset from HTTP headers is just a weird special case 
> > > for a few text resource types. If we were going to deprecate HTML, 
> > > XML and CSS, but keep appcache manifest going forward, it could 
> > > maybe make sense.
> > 
> > What's the advantage of introducing all the pain and suffering that 
> > encodings will inevitably bring with them to the cache manifest 
> > format?
> 
> Just what I said before - the ability to use the same code path for 
> decoding manifests as for decoding other types of resources. It's a 
> minor benefit, admittedly, but it's a potential issue at all stages - 
> from generating content to checking it with automated tools to consuming 
> it.
> 
> For authors and admins, it may be a nuisance to maintain an UTF-8 text 
> file if the rest of the site is in a different encoding.

I believe the long-term benefit of not having to deal with encodings, 
ever, for manifests, outweighs the medium-term benefit of people using 
non-UTF-8 elsewhere. Non-UTF-8 encodings are dropping in usage.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 28 April 2009 22:40:49 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:11 UTC