![\"Windows\/Ubuntu](\"https:\/\/i0.wp.com\/www.tomfotherby.com\/blog\/wp-content\/uploads\/2009\/11\/fontComparison_Georgia_win_ubuntu.png?ssl=1\")
<\/a><\/p>\nThe top one is from IE8 on Windows Vista, whereas the bottom one is from Firefox 3.0.15 on Ubuntu 9.04. On Windows, the text is clearly less pleasant on the eye? It is has jagged edges, has a pixel or two cut off the end of the ‘s’ and is 17 pixels less wide.<\/p>\n
This is the styling code:<\/p>\n
\n#logo h1 {\nfont-family:Georgia, Arial, sans-serif;\nfont-size:50px;\nfont-weight:normal;\nletter-spacing:-0.05em;\nline-height:normal;\n}\n<\/pre>\n<\/p>\n
Problem 1 – Each Operating system ships with a different set of default fonts<\/h3>\n
The Georgia<\/em> font is one of the “core web fonts<\/a>” that everyone has decided should be standard on the web. However, the majority of GNU\/Linux distributions (including Ubuntu) don’t ship with Microsoft’s TrueType core fonts installed (and so don’t have Verdana or Georgia available). Installing them is the quickest way to make web page text render similarly to what people using Windows will see. In Ubuntu, do:
\nsudo apt-get install msttcorefonts<\/span>
\nAccording to a survey on the Ubuntu Forums<\/a>, approximately 75% of Ubuntu users have mscorefonts<\/em> installed. It is one of the first things I do on a fresh Ubuntu install – however, even with mscorefonts<\/em> installed the difference shown above exists.<\/p>\nProblem 2 – Each Operating system renders fonts in it’s own way<\/h3>\n
There is a font rendering standard that everyone has agreed to follow called TrueType<\/a>. If everyone has agreed on a STANDARD<\/strong>, why are there any differences in the way a font looks?<\/p>\nIt is due to different ways of implementing the standard (i.e. different subpixel rendering algorithms):<\/p>\n
\n- Microsoft Windows (as of Vista) uses a rending technology called ClearType<\/a>. The philosopy behind ClearType is to prevent blur and improve readability, even at the cost of not being true to the typeface. Microsoft believes that the shape of each letter should conform to pixel boundaries.<\/li>\n
- Apple uses AAT (Apple Advanced Typography)<\/a>. The philosophy behind ATT is to preserve the design of the typeface as much as possible, even at the cost of a little bit of blurriness.<\/li>\n
- GNU\/Linux uses Freetype<\/a>. Ubuntu enables the subpixel rendering option (i.e. anti-aliasing) in the freetype package but many distributions ship with it disabled due to patent issues.<\/li>\n<\/ul>\n
The Solution<\/h3>\n
There is no good solution but there’s a few things to try:<\/p>\n
\n- Ignore the font difference – work on something important \ud83d\ude09<\/li>\n
- Large serif type faces suffer the most – perhaps you can change to using a font which suffers less?<\/li>\n
- Take a screenshot of the text in the browser which is displaying your text nicely and put the image on the webpage instead of the raw text. This has negative accessibility and SEO implications.<\/li>\n
- Try SIFR<\/a> or cufon<\/a> – I’ve never used them but they seem similar to using a image except they can cope with large amounts of text and solve the accessibility issues.<\/li>\n
- Try FLIR<\/a>, a server-side PHP script that dynamically generates images of text in the font-face of your choosing.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
Look at the difference between these two 50px headers that use the Georgia font: The top one is from IE8 on Windows Vista, whereas the bottom one is from Firefox 3.0.15 on Ubuntu 9.04. On Windows, the text is clearly less pleasant on the eye? It is has jagged edges, has a pixel or two […]<\/p>\n","protected":false},"author":52,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[82],"tags":[85,77,26,84],"class_list":["post-2019","post","type-post","status-publish","format-standard","hentry","category-web-design","tag-css","tag-fonts","tag-ubuntu","tag-webdesign"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/52"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2019"}],"version-history":[{"count":0,"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2019\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2019"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2019"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tomfotherby.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}