<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Josh Hepworth &#187; typography</title>
	<atom:link href="http://www.joshhepworth.com/tag/typography/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joshhepworth.com</link>
	<description>The personal portfolio of [mostly] everything Josh Hepworth</description>
	<lastBuildDate>Fri, 11 Dec 2009 03:46:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Type on the Web</title>
		<link>http://www.joshhepworth.com/type-on-the-web/</link>
		<comments>http://www.joshhepworth.com/type-on-the-web/#comments</comments>
		<pubDate>Thu, 06 Aug 2009 22:31:47 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.joshhepworth.com/?p=347</guid>
		<description><![CDATA[While there has been a big movement recently to get the webfonts format up and running to help break the barrier of traditionally web-safe fonts, there&#8217;s a smaller admittedly less important problem at work. However, that doesn&#8217;t make it any less frustrating as designers move their work from Photoshop to HTML / CSS. There are ]]></description>
			<content:encoded><![CDATA[<p>While there has been a big movement recently to get the webfonts format up and running to help break the barrier of traditionally web-safe fonts, there&#8217;s a smaller admittedly less important problem at work. However, that doesn&#8217;t make it any less frustrating as designers move their work from Photoshop to HTML / CSS.</p>
<p><span id="more-347"></span>There are subtle differences between the way different browsers on different operating systems render the exact same font. While it may not seem like a big deal, it can create big headaches as designers need to choose how to keep their design consistent accross platforms. Since the variation between what browser and operating system a user only becomes greater, I can only see this becoming a larger issue as more people use the different browsers.</p>
<p>While I&#8217;m not going to document the problem extensively here, as Chris Coyier over at CSS Tricks<a title="Browser / OS Font Rendering Differences" href="http://css-tricks.com/font-rendering-differences-firefox-vs-ie-vs-safari/"> documented the rendering differences</a> quite well and a quick look at my own website shows some of the symptoms, I would like to suggest a solution or two as I plan to implement them on my own site.</p>
<p><img class="size-full wp-image-349 alignnone" title="Font Render Compare" src="http://www.joshhepworth.com/wp-content/uploads/2009/08/font-render-compare.gif" alt="Browser Font Render Comparison" width="620" height="143" /></p>
<p>The above shows the subtle differences on my own site when I only change OS. While not an incredible change, those 3 or 4 pixels are terribly annoying every time I see them on my Windows box.</p>
<p><strong>The Fix</strong><br />
Luckily, that specific problem I think I will be able to fix with a relatively small snippet of jQuery JS or PHP magic. While it will rely on the user-agent, which can easily be spoofed, it should be able to fix the issue for the majority of users. I&#8217;ll basically just be grabbing the user-agent OS / Browser, and inject some CSS into the page to adjust the padding / margins of whatever elements it affects. However, I don&#8217;t see this as a solution.</p>
<p><strong>The Solution</strong><br />
My fix will be very site specific even though the principle idea can be applied to any site. A solution should fix it in one swoop, but I do not see that happening for some time. I think the only effective way to solve this issue would be to introduce a &#8220;Web Font Rendering Engine&#8221; that would have to be voluntarily introduced into each browser. Although solving the problem, this is less than ideal considering it would require a browser upgrade and eight years later people are still using IE 6.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.joshhepworth.com/type-on-the-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
