W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > January 2008

RE: Character encoding of linked HTML pages

From: Jo Rabin <jrabin@mtld.mobi>
Date: Fri, 18 Jan 2008 12:50:22 -0000
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B4AD76A1@mtldsvr01.DotMobi.local>
To: <public-mobileok-checker@w3.org>

> type is text/html. Thus it should be OK to use a http-equiv
> header line for declaring the character encoding instead
> of a line in the HTTP header.

Indeed it is OK to omit the charset parameter in this case, but it is
still STRONGLY RECOMMENDED to include one, so only just OK.

Regds
Jo

> -----Original Message-----
> From: Herwig Feichtinger [mailto:hf@isdn-capi.de]
> Sent: 18 January 2008 12:44
> To: dom@w3.org; Jo Rabin
> Cc: public-mobileok-checker@w3.org
> Subject: Re: Character encoding of linked HTML pages
> 
> Hello Jo,
> in fact the _linked_ document is a pure HTML page (in the
> case discussed here), not an XML or XHTML document. Its MIME
> type is text/html. Thus it should be OK to use a http-equiv
> header line for declaring the character encoding instead
> of a line in the HTTP header.
> 
> But I agree that it would cost more resources to read the
> complete HTML page using a HTTP GET command and then scan
> its <head> portion for http-equiv instead of simply checking
> the HTTP response with a HEAD command (assuming that this
> is what the Mobile Checker does).
> 
> Cheers
> Herwig
Received on Friday, 18 January 2008 12:50:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 January 2008 12:50:42 GMT