The interesting thing is that the actual Content-type of my web pages was UTF-8. I look around and found out that my old httpd.conf file had several AddCharset entries while my new server's httpd.conf only had this entry:AddCharset UTF-8 .utf8 After I added several other AddCharset entries to my new webserver's httpd.conf file, it worked.
Thanks to all!!!! Nesto r:-) On Thu, Jun 26, 2008 at 2:56 PM, Néstor <[EMAIL PROTECTED]> wrote: > The apostrophes are inside the html file. > The encoding in the browser is UTF-8 > > I just took a look at the page info on the old webser and the > encoding is set to ISO-8859-1 > > The files were originally created using dreamweaver and were FTP > to the RHEL3 system. > > I do not remember where we are setting the > Content-Type: text/html;charset=ISO-889-1 > for all the files. > > Thanks, > > Nestor :-) > > > > > On Thu, Jun 26, 2008 at 1:36 PM, David Brown <[EMAIL PROTECTED]> wrote: > >> On Thu, Jun 26, 2008 at 11:53:32AM -0700, Néstor wrote: >> >> I took my host backups and untared it to discover that the apostrophe >>> characters have >>> been converted to a character "<92>". I seen this via a web browser or >>> gvim. >>> >> >> Are these apostrophes inside of filenames or in the contents of a file? I >> wouldn't be surprised about the filenames. Hex 92 is the windows-1252 >> encoding for the right-apostrophe, which if your decoded name has a >> different encoding might not be representable. >> >> If it's inside of files themselves, the are probably not being displayed >> with the right encoding. You might be able to select the windows-1252 >> codepage in your webbrowser, or be able to convert the files with >> 'recode'. >> >> David >> >> >> -- >> [email protected] >> http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list >> > > -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
