Hi, In article <004201c2b680$92adad80$0a00a8c0@kb2qzv>, Benedykt P. Barszcz <kb2qzv@poczta.wp.pl> wrote:
I am wondering whether it is necessary to include a META tag in every translated template file in order to force browsers to set proper character encodings for charsets other than iso-8859-1 ?
This depends on the browser. In any case, if the user saves the page, the META tag would become the only way the browser can know what charset the page is in. Preferably, the httpd server (Apache or other) should not send a Content-Type header that is in conflict with what the META tag says; otherwise, the behaviour is undefined (i.e., it depends on the browser... good luck).
If so, could anyone tell me what would be the appropriate way to do so...?
Say if the page should be in ISO-8859-2, the correct META tag should be <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
There is another solution that I know of...namely the apache config file accepts a directive to serve each page with an http header instructing browsers about charsets. But that would probably force only one language in a koha site (installation).
No, I don't think it will force one language in a Koha site, but, if used solely, it would force the site to use Apache, which I don't think is a good thing to do; i.e., IMHO the Apache directive should be used in addition to the META tag. -- Ambrose Li <a.c.li@ieee.org> http://ada.dhs.org/~acli/cmcc/ http://www.cccgt.org/ DRM is theft - We are the stakeholders