also, the encoding isn't set automatically as of now, and <DEFANGED_meta charset="iso-8859-8-i"> will help. (Yes, we need the ISO name here, all the browsers support it, and not all of them support the windows-1255)
Errrmmm... Xsltproc does not support iso-8859-8-i, and therefore the output file is labled to use iso-8859-8. ;) That meta tag is autoganarted by xsltproc. So it is still a question for me, that how can xsltproc output the text in the right (reversed aka logical) order while stamping it as visual... Huh... The only one thing I can think of is that what xsltproc says to be visual is in fact logical odering... Or I don't know how this can happen...
Are you sure that this is what it did? Perhaps the pages with iso-8859-8 are old ones that weren't generated by xsltproc (or something like that...?) At any case, iso-8859-8-i is PREFERRED as the meta charset, but windows-1255 is also OK, because most popular browsers (mozilla, opera, IE) understands that name...
Also, if I am not wrong, putting <html dir="rtl"> enforces charset iso-8859-8-i (because RTL makes the browser render the page from right to left, and this is actually, what iso-8859-8-i *means*). So perhaps putting that HTML tag should be sufficient.
Please reread what I have written. You are talking about meta tags while I was talking about text (content).
Goba