Accesskey n skips to in-page navigation. Skip to the content start.
The series of tests for which we are reporting results checks whether a user agent recognizes that a file declared as US-ASCII is really UTF-8 encoded, and displays the text as UTF-8 regardless of other encoding declarations.
See the results below for user agents tested. This section summarizes the results of those tests.
Note that ignoring the encoding declarations in this way is not behavior that is expected in W3C specifications. In fact, the Character Model for the World Wide Web: Fundamentals very clearly requires the contrary.
Opera 9 treated text as UTF-8, regardless of the encoding declarations in HTTP and meta element, whether or not a UTF-8 signature was present.
IE6 did so only if a UTF-8 signature was present.
The other user agents tested did not display the text as UTF-8.
See the test pages for descriptions of the tests. This page summarizes the results only.
'YES' means that the text was displayed as UTF-8. 'no' means that the text was displayed as US-ASCII. 'n/a' means 'not applicable'.
| File: no signature | File: signature | Object: no signature | Object: signature | |
|---|---|---|---|---|
| IE6 | no | YES | no | YES |
| Firefox 2.0 | no | no | no | no |
| Opera 9.0 | YES | n/a | YES | n/a |
| Netscape 8.1.2 | no | no | no | no |
| Netscape 4 | no | no | n/a | n/a |
Tell us what you think (English).
Content first published 2006-12-11. Last substantive update 2006-12-11 13:39 GMT. This version 2006-12-11 13:39 GMT
For the history of document changes, search for results-utf8-recognition in the i18n blog.
Copyright © 2006 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.
New resources