Tex Texin wrote: > The precedence rule that browsers are supposed to follow is that if the > server sets the charset in the http (transmission) protocol, then that > should be used. > If http is not set, then the meta html statement is followed. > So if after changing the meta statement the browser still insists on > defaulting to 8859-1, > Then probably your server is sending the page with http declaring ISO > 8859-1. > > Depending on your apache version, there was a bug in apache a short while > back, where it set the http charset to iso 8859-1, when it shouldn't set > any charset. > > You might try saving the page locally and then opening it with a browser. > Opening it as a local file will eliminate http as a variable.
This is where I'm getting confused. I guess I need to find out how the shared hosting company has its Apache configured (just fired off a support email). Ignoring the new version of the site for a moment, the existing version has no problems when run on the shared hosting (though the meta statement is set to iso-8859-1) but does have a problem when run on my local system - exactly the same page using exactly the same MySQL data. So it's got to be an Apache config issue, no? Sounds like maybe the shared hosting has Apache set to utf-8. All the accented chars that are giving me problems are in data stored in MySQL tables, so I can't just open a page as a file with the browser - it needs to go via PHP. Appreciate you taking your time with this, BTW. -- @+ Steve -- PHP Internationalization Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
