![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
On the other hand most browsers by now expose a property like document.characterSet (Mozilla) or document.charset (IE) which should give you the charset the browser has taken from the meta or from real HTTP headers. |

#2
| |||||||
| |||||||
|
|
Martin Honnen wrote: ... On the other hand most browsers by now expose a property like document.characterSet (Mozilla) or document.charset (IE) which should give you the charset the browser has taken from the meta or from real HTTP headers. Is it true that these metatags have often different values compared to what the browser actually uses? |
|
And the page author might have not a correct idea of the character set, which the server is sending, thus believing that putting something to metatags the server obeys him/her. |
|
The browsers in this mess try to conclude the character set by examining the byte stream with heuristic rules, |
|
getting often somewhat correct results. |
|
I thought earlier that metatags are commands to the server: |
|
if I put ISO-8859-10 to the tag, then the server transforms the page to that characterset! Eg javascript files on the server: I suspect most authors here have not 100 % reliable and true info which characterset they have. |
At least I have not![]() |
![]() |
| Thread Tools | |
| Display Modes | |
| |