Bruce Momjian wrote:
> Andrew Sullivan wrote:
>> On Fri, Aug 22, 2008 at 02:03:49PM -0400, Bruce Momjian wrote:
>>>> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"
>>>> />
>>> You saw that in our CVS HTML file that is part of the source
>>> distribution? That is the master copy.
>> No, that's my point. When I look at the web page source, it's UTF-8.
>> And since that's the only realistic way to have the framework document
>> around the FAQ, it seems reasonable to me.
>>
>>> I see lots of FAQs in CVS that are not UTF8:
>>>
>>> FAQ.html: <META http-equiv="Content-Type" content="text/html; charset=US-ASCII">
>> This doesn't matter, because US-ASCII is a proper subset of UTF-8.
>>
>>> FAQ_brazilian.html: <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
>> This doesn't need to change because the bottom range of Unicode was made
>> the same as ISO 8859-1 in order to make the transition somewhat easier.
>>
>>> FAQ_polish.html: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
>>> FAQ_russian.html: <META http-equiv="Content-Type" content="text/html; charset=koi8-r">
>>> FAQ_turkish.html: <meta http-equiv="Content-Type" content="text/html; charset=iso8859-9">
>>>
>>> Do they all have to be converted?
>> Those three do, I expect. They sure look like it on the page. All
>> sorts of "?" in there.
>
> Well, something is converting them to UTF8 headings on our web site and
> I thought the HTML encoding was converted at that stage.
Whatever process is taking the FAQ documents and integrating them with
the web layout around it needs to run an encoding conversion.