<?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: Embedded Fonts &#8211; A Bad Idea</title>
	<atom:link href="http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/</link>
	<description>Usable Web Applications with Web Standards</description>
	<lastBuildDate>Tue, 27 Jul 2010 20:50:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ron van den Boogaard</title>
		<link>http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/comment-page-1/#comment-574</link>
		<dc:creator>Ron van den Boogaard</dc:creator>
		<pubDate>Sun, 04 Jan 2009 11:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/#comment-574</guid>
		<description>I tend to disagree here; the more tools proficient designers get the better and any tool the ignorent designers get; they will budge those up.

However I recently ran into another issue, which makes an argument against implementing @font-face. When implementing this on a news-site where we had an .otf licensed to us, it turned out that the IE-variations were trying to make the http call to the font and of course couldn&#039;t, thereby slowing down performance for these browsers. Which made us decide to pull this feature.</description>
		<content:encoded><![CDATA[<p>I tend to disagree here; the more tools proficient designers get the better and any tool the ignorent designers get; they will budge those up.</p>
<p>However I recently ran into another issue, which makes an argument against implementing @font-face. When implementing this on a news-site where we had an .otf licensed to us, it turned out that the IE-variations were trying to make the http call to the font and of course couldn&#8217;t, thereby slowing down performance for these browsers. Which made us decide to pull this feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Walsh</title>
		<link>http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/comment-page-1/#comment-567</link>
		<dc:creator>Josh Walsh</dc:creator>
		<pubDate>Sat, 13 Dec 2008 17:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/#comment-567</guid>
		<description>@Wolfgang - Not harsh at all.  In fact, I agree with you, mostly.

The vast majority of all websites are still built by amateurs.  The top websites have higher quality, and these websites will have extra flexibility in their designs while still taking the user experience into consideration.

I fear the impact on small online businesses the most.</description>
		<content:encoded><![CDATA[<p>@Wolfgang &#8211; Not harsh at all.  In fact, I agree with you, mostly.</p>
<p>The vast majority of all websites are still built by amateurs.  The top websites have higher quality, and these websites will have extra flexibility in their designs while still taking the user experience into consideration.</p>
<p>I fear the impact on small online businesses the most.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wolfgang Löer</title>
		<link>http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/comment-page-1/#comment-566</link>
		<dc:creator>Wolfgang Löer</dc:creator>
		<pubDate>Sat, 13 Dec 2008 11:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/#comment-566</guid>
		<description>Ah, interesting perspective!

Its true, that the freedom of font-choice will lead to many bad choices and many worse sites especially on the private/amateur level.

But i don&#039;t agree with your overall negative verdict - i like to rather see the possibility of improvements on the higher/pro-level websites and especially my new possibilities as a professional web designer/developer.

Some counter-arguments:

a)&quot;web designers are not great at typography&quot;:
- at least where i work your &quot;specialized labor&quot; (very good concept indeed) wouldn&#039;t really be comprimised. we already often enough get layout-screens from rather traditional designers (i.e. with typography-experience). they will be happy about the new options!

b)&quot;we use fonts that experienced typographers have put together for us&quot;
- uh, sort of. there is a grand total of like nine fonts/families of web-significance, half of which are good/ok to use for normal reading-text. those fonts were done by professionals but they are far from being &quot;the definite best possible web-fonts&quot;; we use them, because they are the only options period.

For creative Headings, very small Text or for example handwriting-type there is no choice at all.

the ability to finally make new usable web-fonts will certainly lead to many new and even free (think opensource programming) pro-level fonts for various uses.

c) licensing
This sadly is a problem. it exists, because the fonts once downloaded can&#039;t be protected from other uses by the client. 
the lone fact that millions will see it (on a website) shouldn&#039;t be a problem however, since you also can produce and distribute infinite print-products, from your one pc-license without additional fees.

d) professional fonts will be cost-prohibitive
- if they will be similarly costed to font-licenses for print, i don&#039;t see why (professional) web-designers couldn&#039;t afford what print-designers have for ages.

also i expect the browsers to offer options like &quot;no custom fonts&quot; etc. so you can default to the usual webfonts if it gets all too bad.

Hope, i didn&#039;t sound too harsh :)

Best Greetings,
Wolfgang</description>
		<content:encoded><![CDATA[<p>Ah, interesting perspective!</p>
<p>Its true, that the freedom of font-choice will lead to many bad choices and many worse sites especially on the private/amateur level.</p>
<p>But i don&#8217;t agree with your overall negative verdict &#8211; i like to rather see the possibility of improvements on the higher/pro-level websites and especially my new possibilities as a professional web designer/developer.</p>
<p>Some counter-arguments:</p>
<p>a)&#8221;web designers are not great at typography&#8221;:<br />
- at least where i work your &#8220;specialized labor&#8221; (very good concept indeed) wouldn&#8217;t really be comprimised. we already often enough get layout-screens from rather traditional designers (i.e. with typography-experience). they will be happy about the new options!</p>
<p>b)&#8221;we use fonts that experienced typographers have put together for us&#8221;<br />
- uh, sort of. there is a grand total of like nine fonts/families of web-significance, half of which are good/ok to use for normal reading-text. those fonts were done by professionals but they are far from being &#8220;the definite best possible web-fonts&#8221;; we use them, because they are the only options period.</p>
<p>For creative Headings, very small Text or for example handwriting-type there is no choice at all.</p>
<p>the ability to finally make new usable web-fonts will certainly lead to many new and even free (think opensource programming) pro-level fonts for various uses.</p>
<p>c) licensing<br />
This sadly is a problem. it exists, because the fonts once downloaded can&#8217;t be protected from other uses by the client.<br />
the lone fact that millions will see it (on a website) shouldn&#8217;t be a problem however, since you also can produce and distribute infinite print-products, from your one pc-license without additional fees.</p>
<p>d) professional fonts will be cost-prohibitive<br />
- if they will be similarly costed to font-licenses for print, i don&#8217;t see why (professional) web-designers couldn&#8217;t afford what print-designers have for ages.</p>
<p>also i expect the browsers to offer options like &#8220;no custom fonts&#8221; etc. so you can default to the usual webfonts if it gets all too bad.</p>
<p>Hope, i didn&#8217;t sound too harsh <img src='http://www.designinginteractive.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Best Greetings,<br />
Wolfgang</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Sedor</title>
		<link>http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/comment-page-1/#comment-33</link>
		<dc:creator>Danny Sedor</dc:creator>
		<pubDate>Wed, 10 Oct 2007 01:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/design/embedded-fonts-a-bad-idea/#comment-33</guid>
		<description>&lt;p&gt;Oh. Joy. :(&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Oh. Joy. <img src='http://www.designinginteractive.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
