- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 18 Nov 2011 14:10:36 +0100
- To: Simon Pieters <simonp@opera.com>
- CC: Bjoern Hoehrmann <derhoermi@gmx.net>, Anne van Kesteren <annevk@opera.com>, www-archive@w3.org, public-Webapps@w3.org, Arthur Barstow <art.barstow@nokia.com>
On 2011-11-18 14:04, Simon Pieters wrote: > On Fri, 18 Nov 2011 13:46:16 +0100, Julian Reschke > <julian.reschke@gmx.de> wrote: > >> That's fine if you use a new type, or profile an existing one. >> >> But claiming that charset=... means something else before depending on >> the context it's used in is asking for trouble. > > What kind of trouble? Trouble that other recipients disagree on that the encoding is. >>> Just use UTF-8. If you can't use UTF-8 in your workers, use ASCII and >>> character escapes. AFAIK there's have been no requests to support legacy >>> encodings in workers in Opera. >> >> I'm ok with that. I'm not ok with treating something that has a >> charset of ISO-8859-1 silently as UTF-8, in particular when other >> parts of the platform disagree. > > Why not? We have context-dependent treatment of MIME types already (e.g. > a text/html resource can be treated as a script). These are workarounds because of legacy, I assume. Workers are a new feature. Best regards, Julian
Received on Friday, 18 November 2011 13:11:08 UTC