I wrote:
Johannes wrote:
Some websites seems to send images with a charset set in the header, e.g: Content-Type: image/jpeg;charset=ISO-8859-1 In that case dillo seems to decode the data resulting in: Not a JPEG file: starts with 0xc3 0xbf Not sure whether we can/want to do anything about that.
It seems like it would make sense to restrict decoding to text/*. I'll look in the rfc to see whether it says something relevant.
Fix committed. RFC 2046 defines a charset parameter for text/* (and it's also mentioned in the RFCs for text/html and text/css media types). Nothing mentions any parameters defined for image/*, or for the specific image types that dillo displays. Interestingly, I learned of RFC 5147, which is a proposed standard involving URI fragments and text/plain: http://tools.ietf.org/html/rfc5147#section-5