On Thu, 28 Jun 2012, Stuart Henderson wrote:
>On 2012-06-28, ropers <rop...@gmail.com> wrote:
>> On 28 June 2012 01:17, Andres Perera <andre...@zoho.com> wrote:
>>>> A http://www.openbsd.org/papers/bsdcan11-mandoc-openbsd.html
>>>
>>>
>>> that page is encoded iso 8859-1, doesn't state so anywhere, breaks
>>> with browsers configured to default to utf8 in the absence of encoding
>>> qualifiers
>>
>> $ telnet www.openbsd.org 80
>> Trying 142.244.12.42...
>> Connected to www.openbsd.org.
>> Escape character is '^]'.
>> GET /papers/bsdcan11-mandoc-openbsd.html HTTP/1.1
>> Host: www.openbsd.org
>>
>> HTTP/1.1 200 OK
>> Date: Wed, 27 Jun 2012 23:59:19 GMT
>> Server: Apache
>> Last-Modified: Sat, 18 Jun 2011 11:11:28 GMT
>> ETag: "65f60c9352dee7ec594696cdfb681e86316269ef"
>> Accept-Ranges: bytes
>> Content-Length: 32754
>> Content-Type: text/html
>>
>><HTML>
>><BODY>
>> ...
>>
>>
>> Okay, this could transmit "Content-Type: text/html;
>> charset=iso-8859-1" but doesn't, but that's ok, we can do this on a
>> page-by-page basis with a META tag, which ought to be ignored by
>> browsers that don't understand it:
>
>IMO if it's worth doing this at all, it needs doing to *all* pages
>that need it, in one go, consistently.
>
>Anything else is likely to be way too much pain for the translators.
Using META is _ugly_, especially for specifying a charset (since the
page will be read up through the META element using the charset
specified in the real header or assumed by the browser -- and that
charset could be incompatible with the actual encoding.) Why not just
use the AddDefaultCharset directive to ensure that a charset is
specified in the real header for all pages? Or is this known to break
some browsers that are still in use?
Dave
--
Dave Anderson
<d...@daveanderson.com>
