public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Andrew Sullivan <[email protected]>
Cc: [email protected]
Subject: Re: [BUGS] BUG #4279: Bad codepage in our web-site
Date: Mon, 15 Sep 2008 10:29:36 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

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.

view thread (13+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [BUGS] BUG #4279: Bad codepage in our web-site
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox