Monthly Archives: July 2007

This article was largely rewritten to provide greater clarity, and further information about how to detect and remove a UTF-8 signature.

Changes include a new title and question, and the integration of the former background section into the answer.

This tutorial was updated to reflect the fact that IE7 no longer flips into quirks mode when an XML declaration is used. For a detailed list of changes read the full post.

The following paragraphs were changed as shown by the ins and del markup.

<p>In browsers such as <ins>Internet Explorer 7, Firefox,</ins><del>Mozilla</del>, Netscape, Opera, and others, with or without the XML declaration, a page served with a DOCTYPE declaration will be rendered in standards mode.</p>
<p> With Internet Explorer<ins> 6</ins>, however, if anything appears before the DOCTYPE declaration the page is rendered in quirks mode. </p>
<p>Because Internet Explorer <ins> 6</ins> users <ins>still</ins> count for a very large proportion of browser users, this is a significant issue. If you want to ensure that your pages are rendered in the same way on all standards-compliant browsers, you need to think carefully about how you deal with this.</p>
<p>The presence of an XML declaration in an XHTML 1.0 file served as HTML will cause your file to be rendered in quirks mode on Internet Explorer <ins> 6</ins> (and therefore for a potentially large proportion of your audience).</p>

This article was updated to reflect the fact that IE7 no longer flips into quirks mode when an XML declaration is used. For a detailed list of changes read the full post.

The following paragraphs were changed as shown by the ins and del markup.

<p>In browsers such as <ins>Internet Explorer 7, Firefox,</ins><del>Mozilla</del>, Netscape, Opera, and others, with or without the XML declaration, a page served with a DOCTYPE declaration will be rendered in standards mode.</p>
<p> With Internet Explorer<ins> 6</ins>, however, if anything appears before the DOCTYPE declaration the page is rendered in quirks mode. </p>
<p>Because Internet Explorer <ins> 6</ins> users <ins>still</ins> count for a very large proportion of browser users, this is a significant issue. If you want to ensure that your pages are rendered in the same way on all standards-compliant browsers, you need to think carefully about how you deal with this.</p>
<p>The presence of an XML declaration in an XHTML 1.0 file served as HTML will cause your file to be rendered in quirks mode on Internet Explorer <ins> 6</ins> (and therefore for a potentially large proportion of your audience).</p>
The following list item was added to the Further Reading section:
<li><p><a href=”http://msdn2.microsoft.com/en-us/library/Bb250496.aspx”>Cascading Style Sheet Compatibility in Internet Explorer 7</a> <span class=”uri”>http://msdn2.microsoft.com/en-us/library/Bb250496.aspx</span></p></li>

Translators should retranslate the article.

Thanks to A.Osobka and N.Fabisz the FAQ-based article “HTML, XHTML, XML and Control Codes” has now been translated into Polish (language negotiated).

Thanks to A.Osobka and N.Fabisz the FAQ-based article “Styling using the lang attribute” has now been translated into Polish (language negotiated).

Thanks to A.Osobka and N.Fabisz the article “Introducing Character Sets and Encodings” (part of the Getting Started series) has now been translated into Polish (language negotiated).

At the request of Mark Davis, added the text:

“See also ICU4J since it contains more up-to-date data (and more functionality) than the JDK routines.”

FAQ-based article: How can I ensure that when text expands in translation the background images will still work?

By Richard Ishida, W3C.

When text is translated from one language to another, the length of the source and translated text is likely to be different. This article provides background material that will briefly explore some of the systematic differences.

By Richard Ishida, W3C.