you should also be able to add/edit a .htaccess file on the shared web space and add the following:

AddDefaultCharset utf-8

most hosts, even shared hosts should allow this (and it saves adding php headers to every page)

Thanks,

David

On 7/7/09 18:46, Nick Roper wrote:
Hey Rimantas,

I added a line of PHP code as follows:

<?php header("Content-Type:text/html; charset=UTF-8"); ?>

and it works fine now.

I also installed Live Headers in FF for future debugging.

Many thanks for that.

Cheers,

Nick

Rimantas Liubertas wrote:
Here's the issue:

We are working on a site that incorporates Russian text. It displays OK on
our development server, but when transferring the files to the live server
we get garbled output.
<…>
However, the same file uploaded to the live server displays the last menu
item incorrectly:

http://www.imperial-russian-dating.com/utf8-test.php

The file has been saved as utf8 encoded in the editor (Komodo) and then
uploaded to each server.

Any ideas ?
There are headers sent by your live server:
Connection:close
Content-Length:862
Content-Type:text/html; charset=ISO-8859-1
Date:Tue, 07 Jul 2009 16:22:43 GMT
Server:Apache/2.2.3 (CentOS)
X-Powered-By:PHP/5.1.6

Take a look at Content-Type header: it specifies charset as iso-8859-1. Charset
specified in HTTP has preference over charset in META. If you have
access to your
server configuration look for AddDefaultCharset directive in Apache
config. You can either
change it to UTF or comment it out.

Regards,
Rimantas
--
http://rimantas.com/


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************





*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************

Reply via email to