Anton Bar wrote:
Yes. Server (in our case IIS) sends only content type (text/html) and
length.
You should really send the character set in the header... e.g.
Content-Type: text/html; charset=utf-8
if you are using UTF-8 as charset.
___
mozilla-embe
>> A short test with nsIDOMNSDocument.charset property shows that the
>> embedded window uses an incorrect charset despite the fact we
>> specifically state the Hebrew charset in a META tag.
>
> Is this happening over HTTP? What headers does the server send?
Yes. Server (in our case IIS) sends
Anton Bar wrote:
Is there any way to make the embedded browser to display some specific
encoding or to detect the META correctly?
What the "Character set" menu in Mozilla does is QI the docshell to
nsIDocCharset, set its charset property, and reloads with the
nsIWebNavigation::LOAD_FLAGS_CHAR
Anton Bar wrote:
A short test with nsIDOMNSDocument.charset property shows that the embedded
window uses an incorrect charset despite the fact we specifically state the
Hebrew charset in a META tag.
Is this happening over HTTP? What headers does the server send?
Is there any way to make the
Hi all,
We embed mozilla and it works fine with western encodings and Unicode.
However, when we use documents in Hebrew Windows-1255 encoding, the text is
displayed as question marks.
A short test with nsIDOMNSDocument.charset property shows that the embedded
window uses an incorrect charset d
