[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: i18n.kde.org: problem with encoding
From:       Federico Cozzi <federicocozzi () federicocozzi ! it>
Date:       2003-02-07 17:20:52
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 7 Feb 2003, Nguyen Vu Hung wrote:

> I think it's a bug with Debian apache but I have to report the problem
> here.  i18n.kde.org's apache server does not set encoding to "UTF-8"
> even I declared it in HTML file header. Encoding turn out to be "Western
> ISO-8859-1".

Sometimes this happens because both the HTTP server AND the HTML page are
saying their encoding. The standard says that, should this happen, the
server wins.
I once encountered this problem with an Apache server, it was caused by
the "AddDefaultCharset" directory which was turned on. My personal opinion
is that the server should not say the encoding of the pages
("AddDefaultCharset off"), leaving the choice to the page or to the
browser.
As a workaround, usually you can put an ".htaccess" file in your root
directory, with "AddDefaultCharset off".
BTW, in the HTML you should put the charset definition BEFORE the title.

Hope this helps.

- -- 
Federico Cozzi
http://www.federicocozzi.it/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+Q+r5cFFOofFSVBARAsoQAJ0erwDAcsrhOhJp1gqGSdST/GkD3gCdH0ck
twHZIVVY2ZjDvQyiHoU3SBA=
=tIny
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread]