Character encoding problems

Any one have character encoding problems on dreamhost?

I change my meta tag to

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

from utf-8 and not my characters are displaying fine before in firefox I'd have a diamond question mark on the ' and - symbols.

I take it this is ok since this meta tag resolved the issue
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

I'm using zend to save my html files

Any one have feedback or suggestions?

 

Use a server-side programming language like PHP and over-ride the server's character encoding by setting a HTTP-HEADER string at the top of your Web pages (this does not get displayed in the browser, but gets sent to it).

 

You have an example?

 

Not on-hand, but if you search in your search engine of choice, I'm sure you'll find one.

 

by changing char enconding in meta tags does in NO way change the originally CREATED/saved/uploaded character encodings !!

example
if once you created/uploaded a UTF8 file and want it now to be ISO-8859-1 - then in addition to the change of meta tag you also need to CONVERT the entire file - ALL files -
see
http://www.kriyayoga.com/love_blog/post.php/224

and you also should have the correct apache charset default config OR at least in your .htaccess

such line would look like

AddDefaultCharset utf-8

or

AddDefaultCharset ISO-8859-1

changing existing charset from utf8 to OTHERS makes no real sense unless you KNOW why and have a good reason.

if however you have problems using utf8 after host change OR machine change - a simple correction of the apache/.htaccess may solve your problem and serve all files correctly
provided all files are correctly marked as the charset you actually created it with or CONVERTED it into.

 

Won't do him a bit of good if his server is IIS or Xitami (though the principle is still the same - the implementations are worlds apart from what I understand).

 

whatever server he has
changing meta tags for char encoding ALWAYS also requires CONVERTING the actual content-file by whatever tool available on HIS online and/OR offline system

 

yes I fixed it I had to change the meta tag over to utf8 and save the document as a utf8 zend default does not save it as a utf 8

 

Gah, I thought I had quoted the part referencing Apache. But yeah, you are right about the file itself. I was only referring to the part of the post that was talking about the Apache Web server itself.

Sorry for the confusion.