P
Provost Zakharov
Hello,
I just needed some help on how the DOM is encoded by the IE
parser.
As per the MSDN page,
http://msdn.microsoft.com/workshop/author/dhtml/reference/charsets/charset4.asp
,server encodings are considered first,then the <meta> tag specified
encodings and then finally the user's preferred settings(which is
usually Western-European aka windows-1252).
I used Ethereal to packet sniff the traffic to www.baidu.com .There is
no encoding specified in the content-type header on this site .Also,
the preferred encoding is specified in the <meta> tags as gb2312
..However ie.Document.charset returns the value windows-1252.
My question is this...which encoding is being used by the parser to
actually encode the page?Is it the default user encoding or the <meta>
tag encoding?And if the default user encoding is being used to encode
the content ,isn't that contradictory to what is specified on the page
above?
Thanks
Provost Zak
I just needed some help on how the DOM is encoded by the IE
parser.
As per the MSDN page,
http://msdn.microsoft.com/workshop/author/dhtml/reference/charsets/charset4.asp
,server encodings are considered first,then the <meta> tag specified
encodings and then finally the user's preferred settings(which is
usually Western-European aka windows-1252).
I used Ethereal to packet sniff the traffic to www.baidu.com .There is
no encoding specified in the content-type header on this site .Also,
the preferred encoding is specified in the <meta> tags as gb2312
..However ie.Document.charset returns the value windows-1252.
My question is this...which encoding is being used by the parser to
actually encode the page?Is it the default user encoding or the <meta>
tag encoding?And if the default user encoding is being used to encode
the content ,isn't that contradictory to what is specified on the page
above?
Thanks
Provost Zak