Another note I forgot, which might help solve the bug:

The page has content-encoding problems: It is marked as "ISO-8859-8" in its 
HTTP headers, but includes a meta tag declaring  it as "windows-1255" 
(Windows-1255 is essentially ISO-8859-8-I, which differs from ISO-8859-8 in 
its BiDi properties); the correct encoding is Windows-1255.

While this problem legitimately leads to rendering problems (i.e. for most 
rendering problem, we have to say that the problem is in the page, not in the 
browser), one does expect consistency between the normal page view and the 
print preview.

Thanks,
        Shai.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to