StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I guess you have also found this one: <a href="http://code.google.com/p/googlefontdirectory/issues/detail?id=1" rel="noreferrer">http://code.google.com/p/googlefontdirectory/issues/detail?id=1</a><br> (there was a post today regarding to Francois One, I guess it was yours)</p> <p>There is a solution that works for me(I see the font now in IE6-9)</p> <p><em>The most common reason fonts don't load in IE is because the font name table was coded wrong by the font author. That is definitely the case with Josefin. The Family Name + the Style Name must = The Full Name. Josephine fails this. FYI - fontsquirrel.com automatically corrects these problems in their webfonts.</em></p> <p>This must be the reason, some wrong naming inside the original font which matters to IE</p> <ol> <li>Downloaded the TTF from <a href="http://googlefontdirectory.googlecode.com/hg/francoisone/" rel="noreferrer">google</a> </li> <li>Uploaded the font at <a href="http://www.fontsquirrel.com/fontface/generator" rel="noreferrer">fontsquirrel.com</a> and got my "@font-face-kit"</li> <li>Uploaded the created .eot inside the Kit</li> <li>Edited the css regarding to <a href="http://www.fontspring.com/blog/further-hardening-of-the-bulletproof-syntax" rel="noreferrer">this bulletproof syntax</a> </li> </ol> <p>I changed only the URLs of the EOTs to my uploaded font, for the WOFF I still may use the google-font(But i guess it's better to use own files for every font, nobody knows how long the specific fonts will be reachable via the current URLs).</p> <p>Also Note: the font-family-name to use inside the CSS has changed now to <strong>FrancoisOneRegular</strong> </p> <p><strong><a href="http://jsfiddle.net/doktormolle/nLUgJ/" rel="noreferrer">http://jsfiddle.net/doktormolle/nLUgJ/</a></strong></p>

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