My mozilla displays the /he2/ files improperly. Though Kokqueror uses
the right encoding. If I use
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-8-I">
[...]
Yes. php.net will have a HTTP header, the offline version should have a
proper <meta>.
In reference to
http://www.iana.org/assignments/character-sets
<meta http-equiv="Content-Type" content="text/html; charset=WINDOWS-1255">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-8-I">
are allowed. The latter was not tried, because xsltproc complains about :-)
If the latter is preferred for offline html, configure.in needs some tweaks.
But to let this looooooong thread come to an end:
he guys should definitley answer the question, which charset is preferred:-) and displays the content properly. Thats all, I think:-)
Imho, windows-1255 should be used as output encoding in xsltproc, and an automatic find&replace should replace all windows-1255 to iso-8859-8-i in the files, as this works in Mozilla (and probably in other browsers too, I have only tested this with Mozilla and Konqueror).
The <meta> tag is added automatically by xsltproc, there are no rules for that in the stylesheets. The XSLT spec defines the HTML output method to automatically add a <meta> tag:
http://www.w3.org/TR/xslt#section-HTML-Output-Method
Therefore this can only be dealt with after the XSLT processing is ready, and not in the stylesheets IMHO.
Goba