StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>To answer your question directly:</p> <blockquote> <p><strong>ClearType font rendering is used in all IE9 document modes; sub-pixel positioning is used only in IE9’s default standards mode. IE9’s compatibility modes—Quirks, 7, and 8—use whole-pixel text metrics.</strong></p> </blockquote> <p>So try switching your doctype to use <a href="http://en.wikipedia.org/wiki/Quirks_mode" rel="nofollow noreferrer">Quirks mode</a>:</p> <pre><code> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> </code></pre> <p>The other thing to consider is to try avoid <a href="http://www.hanselman.com/blog/TheUltimateGuideOfFiveThingsForNewIE9UsersWhoFearChange.aspx" rel="nofollow noreferrer">point based font sizes</a>. <hr/></p> <h3>Important information regarding fonts, blurriness and rendering in IE9</h3> <ul> <li><a href="https://stackoverflow.com/questions/5558773/ie-9-text-renders-very-poorly-is-there-a-workaround/5639736">IE 9 does not use sub-pixel antialiasing under certain conditions</a></li> </ul> <p>MSDN sources:</p> <ul> <li><a href="http://blogs.msdn.com/b/ie/archive/2010/11/03/sub-pixel-fonts-in-ie9.aspx" rel="nofollow noreferrer">Sub-pixel Fonts in IE9 - blogs.msdn.com/b/ie/archive/2010/11/03/sub-pixel-fonts-in-ie9.aspx</a></li> <li><a href="http://www.hanselman.com/blog/TheUltimateGuideOfFiveThingsForNewIE9UsersWhoFearChange.aspx" rel="nofollow noreferrer">IE9's blurry font text - www.hanselman.com/blog/TheUltimateGuideOfFiveThingsForNewIE9UsersWhoFearChange.aspx</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/cc288325%28VS.85%29.aspx" rel="nofollow noreferrer">Defining Document Compatibility</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/ff955379%28v=VS.85%29.aspx" rel="nofollow noreferrer">Documents Mode</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload