<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Boing Boing Redesign Uncovers Web Font Ignorance</title>
	<atom:link href="http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/</link>
	<description>the Phinney-us Blog on Typography &#38; Text</description>
	<lastBuildDate>Wed, 11 Aug 2010 21:30:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Sam Foster</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1341</link>
		<dc:creator>Sam Foster</dc:creator>
		<pubDate>Wed, 26 May 2010 08:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1341</guid>
		<description>This has been going on since at least &#039;99 when I got burnt trying to deploy cross-browser web fonts using MS&#039; eot and the bitstream truedoc format that Netscape 4 supported. Font-smoothing was off by default in most Windows of the day, and most fonts didn&#039;t smooth (or anti-alias) below 18pt or so. I.e. they looked like ass on the screen in IE.  

Which left you with a small collection of screen-optimized fonts to choose from, or the prospect of making your own - not a trivial task. Guess which fonts were screen optimized? Yes, our old friends Verdana, Arial, Tahoma etc. Back to square one. 

We were having the same discussions about licensing 10 years ago. Maybe this time around there&#039;ll be a breakthrough? At least nowadays the 100+KB to download a full character set for a font isn&#039;t a deal-breaker.

&lt;em&gt;[There are certainly new approaches which deal with the licensing issues, including http://www.webink.com, the service I&#039;ve helped develop at Extensis.]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>This has been going on since at least &#8217;99 when I got burnt trying to deploy cross-browser web fonts using MS&#8217; eot and the bitstream truedoc format that Netscape 4 supported. Font-smoothing was off by default in most Windows of the day, and most fonts didn&#8217;t smooth (or anti-alias) below 18pt or so. I.e. they looked like ass on the screen in IE.  </p>
<p>Which left you with a small collection of screen-optimized fonts to choose from, or the prospect of making your own &#8211; not a trivial task. Guess which fonts were screen optimized? Yes, our old friends Verdana, Arial, Tahoma etc. Back to square one. </p>
<p>We were having the same discussions about licensing 10 years ago. Maybe this time around there&#8217;ll be a breakthrough? At least nowadays the 100+KB to download a full character set for a font isn&#8217;t a deal-breaker.</p>
<p><em>[There are certainly new approaches which deal with the licensing issues, including <a href="http://www.webink.com" rel="nofollow">http://www.webink.com</a>, the service I've helped develop at Extensis.]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Font Hinting Explained By A Font Design Master</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1104</link>
		<dc:creator>Font Hinting Explained By A Font Design Master</dc:creator>
		<pubDate>Sun, 10 Jan 2010 19:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1104</guid>
		<description>[...] environments they’ve cared about, Type 1 and OpenType CFF fonts render perfectly well on screen:  Boing-Boing-Redesign-Uncovers-Web-Font-Ignorance Just about any application on the Mac OS. Adobe Acrobat, InDesign and Illustrator, on any platform. [...]</description>
		<content:encoded><![CDATA[<p>[...] environments they’ve cared about, Type 1 and OpenType CFF fonts render perfectly well on screen:  Boing-Boing-Redesign-Uncovers-Web-Font-Ignorance Just about any application on the Mac OS. Adobe Acrobat, InDesign and Illustrator, on any platform. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henk Gianotten</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1082</link>
		<dc:creator>Henk Gianotten</dc:creator>
		<pubDate>Sun, 20 Dec 2009 00:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1082</guid>
		<description>I think, there is another major problem by using BPreplay. The lack of characters for non-English languages. It has only 207 characters and only Greek users can display a fair number of their characters. Different character sets and different encodings can increase these problems too. Boing Boing does not know when they want (or have) to show these &quot;strange characters&quot;. In my opinion their designers (and/or web technicians) did a very bad job.</description>
		<content:encoded><![CDATA[<p>I think, there is another major problem by using BPreplay. The lack of characters for non-English languages. It has only 207 characters and only Greek users can display a fair number of their characters. Different character sets and different encodings can increase these problems too. Boing Boing does not know when they want (or have) to show these &#8220;strange characters&#8221;. In my opinion their designers (and/or web technicians) did a very bad job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sex, lies, &#38; type &#124; i love typography, the typography and fonts blog</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1073</link>
		<dc:creator>Sex, lies, &#38; type &#124; i love typography, the typography and fonts blog</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1073</guid>
		<description>[...] Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font IgnoranceWhere to get Web fontsBetter Postscript CFF font rendering with DirectWrite.Typotheque has now [...]</description>
		<content:encoded><![CDATA[<p>[...] Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font IgnoranceWhere to get Web fontsBetter Postscript CFF font rendering with DirectWrite.Typotheque has now [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A giant step for typography on the Web &#124; Type Directors Club</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1062</link>
		<dc:creator>A giant step for typography on the Web &#124; Type Directors Club</dc:creator>
		<pubDate>Tue, 03 Nov 2009 20:21:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1062</guid>
		<description>[...] boingboing.net is a high-profile early adopter of this technology, with mixed reviews and results. This article by Thomas Phinney goes through some of the issues that have come up with BoingBoing&#8217;s implementation of the [...]</description>
		<content:encoded><![CDATA[<p>[...] boingboing.net is a high-profile early adopter of this technology, with mixed reviews and results. This article by Thomas Phinney goes through some of the issues that have come up with BoingBoing&#8217;s implementation of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New developments in web fonts &#124; Type Directors Club</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1058</link>
		<dc:creator>New developments in web fonts &#124; Type Directors Club</dc:creator>
		<pubDate>Sun, 01 Nov 2009 17:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1058</guid>
		<description>[...] boingboing.net is a high-profile early adopter of this technology, with mixed reviews and results. This article by Thomas Phinney goes through some of the issues that have come up with BoingBoing&#8217;s implementation of the [...]</description>
		<content:encoded><![CDATA[<p>[...] boingboing.net is a high-profile early adopter of this technology, with mixed reviews and results. This article by Thomas Phinney goes through some of the issues that have come up with BoingBoing&#8217;s implementation of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lindsey Thomas Martin</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1054</link>
		<dc:creator>Lindsey Thomas Martin</dc:creator>
		<pubDate>Sat, 31 Oct 2009 18:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1054</guid>
		<description>Very helpful article. Thank you. When I read: &#039;many foundries are still trying to figure out how to approach the web fonts conundrum. Will they license fonts for use on web servers directly? Will they do so but specify security requirements that can’t be met by sticking regular desktop fonts on web servers&#039;, it occurred to me that this may be something to which Extensis could apply its expertise in managing fonts.

LTM</description>
		<content:encoded><![CDATA[<p>Very helpful article. Thank you. When I read: &#8216;many foundries are still trying to figure out how to approach the web fonts conundrum. Will they license fonts for use on web servers directly? Will they do so but specify security requirements that can’t be met by sticking regular desktop fonts on web servers&#8217;, it occurred to me that this may be something to which Extensis could apply its expertise in managing fonts.</p>
<p>LTM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sex, lies, &#38; type&#160;&#124;&#160;meshdairy</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1052</link>
		<dc:creator>Sex, lies, &#38; type&#160;&#124;&#160;meshdairy</dc:creator>
		<pubDate>Thu, 29 Oct 2009 07:22:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1052</guid>
		<description>[...] WOFF sample page — you will need the latest development version of FireFox to actually see the fonts at work (or wait until FF 3.6). Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font Ignorance [...]</description>
		<content:encoded><![CDATA[<p>[...] WOFF sample page — you will need the latest development version of FireFox to actually see the fonts at work (or wait until FF 3.6). Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font Ignorance [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sex, lies, &#38; type &#124; More On Design</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1042</link>
		<dc:creator>Sex, lies, &#38; type &#124; More On Design</dc:creator>
		<pubDate>Sun, 25 Oct 2009 22:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1042</guid>
		<description>[...] WOFF sample page — you will need the latest development version of FireFox to actually see the fonts at work (or wait until FF 3.6). Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font Ignorance [...]</description>
		<content:encoded><![CDATA[<p>[...] WOFF sample page — you will need the latest development version of FireFox to actually see the fonts at work (or wait until FF 3.6). Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font Ignorance [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sex, lies, &#38; type &#124; i love typography, the typography and fonts blog</title>
		<link>http://www.thomasphinney.com/2009/10/boing-boing-redesign-uncovers-web-font-ignorance/comment-page-1/#comment-1037</link>
		<dc:creator>Sex, lies, &#38; type &#124; i love typography, the typography and fonts blog</dc:creator>
		<pubDate>Sat, 24 Oct 2009 20:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.thomasphinney.com/?p=417#comment-1037</guid>
		<description>[...] WOFF sample page — you will need the latest development version of FireFox to actually see the fonts at work (or wait until FF 3.6). Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font Ignorance [...]</description>
		<content:encoded><![CDATA[<p>[...] WOFF sample page — you will need the latest development version of FireFox to actually see the fonts at work (or wait until FF 3.6). Let’s hope the other browser vendors get behind it, and start implementing support for WOFF. Boing Boing Redesign Uncovers Web Font Ignorance [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
