<?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"
	>
<channel>
	<title>Comments on: wp-typogrify</title>
	<atom:link href="http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/</link>
	<description>design and programming hybridized</description>
	<pubDate>Thu, 24 Jul 2008 02:44:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: johno</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1997</link>
		<dc:creator>johno</dc:creator>
		<pubDate>Wed, 25 Jun 2008 12:59:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1997</guid>
		<description>Of course, that's why typogrify isn't working for my pages (e.g. my about page). It's not designed to. Is there, then, a way of calling the plugin for individual pages?

Still an amazing plugin.</description>
		<content:encoded><![CDATA[<p>Of course, that&#8217;s why typogrify isn&#8217;t working for my pages (e.g. my about page). It&#8217;s not designed to. Is there, then, a way of calling the plugin for individual pages?</p>
<p>Still an amazing&nbsp;plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Bedford</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1992</link>
		<dc:creator>Karl Bedford</dc:creator>
		<pubDate>Tue, 24 Jun 2008 04:45:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1992</guid>
		<description>Great, great plugin!

Is there a way to allow this script to apply tp WP Pages as well? As far as I can see it currently does not.

Keep up the good work :)

Karl</description>
		<content:encoded><![CDATA[<p>Great, great plugin!</p>
<p>Is there a way to allow this script to apply tp <span class="caps">WP</span> Pages as well? As far as I can see it currently does not.</p>
<p>Keep up the good work :)&nbsp;Karl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Meyer</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1800</link>
		<dc:creator>Kyle Meyer</dc:creator>
		<pubDate>Tue, 22 Apr 2008 20:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1800</guid>
		<description>Hello there,

Thanks for the amazing plugin, it really saves me a lot of time and worry and I install it on every site I have running and those that are in progress.

I did however, notice that if you install it on a site that you have previously manually inserted non-breaking spaces at the end of paragraphs, that it adds yet another one prior to them. This results in three words wrapping to a new line rather than two. Is there anything I can do to remedy the problem without manually removing all of the existing non-breaking spaces?</description>
		<content:encoded><![CDATA[<p>Hello there,</p>
<p>Thanks for the amazing plugin, it really saves me a lot of time and worry and I install it on every site I have running and those that are in progress.</p>
<p>I did however, notice that if you install it on a site that you have previously manually inserted non-breaking spaces at the end of paragraphs, that it adds yet another one prior to them. This results in three words wrapping to a new line rather than two. Is there anything I can do to remedy the problem without manually removing all of the existing non-breaking&nbsp;spaces?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sunday type: ampersand&#160;type &#124; i love typography, the typography blog</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1753</link>
		<dc:creator>Sunday type: ampersand&#160;type &#124; i love typography, the typography blog</dc:creator>
		<pubDate>Sun, 13 Apr 2008 23:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1753</guid>
		<description>[...] wondered how some sites set ampersands (&#38;) in a different typeface? Well, with the typogrify plugin it&#8217;s easy. In the typogrify admin, just check the &#8220;style ampersands&#8221; box, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] wondered how some sites set ampersands (&amp;) in a different typeface? Well, with the typogrify plugin it&#8217;s easy. In the typogrify admin, just check the &#8220;style ampersands&#8221; box,&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamish</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1745</link>
		<dc:creator>Hamish</dc:creator>
		<pubDate>Sun, 13 Apr 2008 00:13:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1745</guid>
		<description>Thanks &lt;a href="http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1743" rel="nofollow"&gt;John&lt;/a&gt; for your response.

&lt;a href="http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1742" rel="nofollow"&gt;Alenônimo&lt;/a&gt;
Thanks for your comment! It's really appreciated.

John gave a good example for the ampersand. I would also add that you might want to use some alternatives as well. I.e.,

&lt;code&gt;.amp { font-family: 'Hoefler Text', 'Palatino Linotype', 'Adobe Caslon Pro', serif; }&lt;/code&gt;

Since the user might not have the exact font you specify.

Another thing I do is lower the font size of anything wrapped in &lt;code&gt;&#60;span class='caps'&#62;&lt;/code&gt;.

&lt;code&gt;.caps { font-size: 85%; }&lt;/code&gt;

It's purely aesthetic. But I like the change.

The original &lt;a href="http://static.mintchaos.com/projects/typogrify/" rel="nofollow"&gt;typogrify demo page&lt;/a&gt; shows some of this in action.</description>
		<content:encoded><![CDATA[<p>Thanks <a href="http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1743" rel="nofollow">John</a> for your response.</p>
<p><a href="http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1742" rel="nofollow">Alenônimo</a><br />
Thanks for your comment! It&#8217;s really appreciated.</p>
<p>John gave a good example for the ampersand. I would also add that you might want to use some alternatives as well. I.e.,</p>
<p><code>.amp { font-family: 'Hoefler Text', 'Palatino Linotype', 'Adobe Caslon Pro', serif; }</code></p>
<p>Since the user might not have the exact font you specify.</p>
<p>Another thing I do is lower the font size of anything wrapped in <code>&lt;span class='caps'&gt;</code>.</p>
<p><code>.caps { font-size: 85%; }</code></p>
<p>It&#8217;s purely aesthetic. But I like the change.</p>
<p>The original <a href="http://static.mintchaos.com/projects/typogrify/" rel="nofollow">typogrify demo page</a> shows some of this in&nbsp;action.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johno</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1743</link>
		<dc:creator>johno</dc:creator>
		<pubDate>Sat, 12 Apr 2008 22:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1743</guid>
		<description>@Alenônimo 
The ligatures thing is interesting. However, it wouldn't look good for all typefaces. For example, if your tesxt is set in Georgia, Georgia doesn't have an st ligature, so you'd get the standard 'unicode' one.

Re the CSS options you could change the ampersand (&#38;) for a pretty one (e.g. Hoefler Text). so, where you have:

&#38;

just use the following CSS rule:

.amp {
font-family: 'Hoefler Text';
font-style: italic;
        }

The italic ampersand in Hoefler Text is gorgeous!</description>
		<content:encoded><![CDATA[<p>@Alenônimo<br />
The ligatures thing is interesting. However, it wouldn&#8217;t look good for all typefaces. For example, if your tesxt is set in Georgia, Georgia doesn&#8217;t have an st ligature, so you&#8217;d get the standard &#8216;unicode&#8217; one.</p>
<p>Re the <span class="caps">CSS</span> options you could change the ampersand (&amp;) for a pretty one (e.g. Hoefler Text). so, where you have:</p>
<p><span class="amp">&amp;</span></p>
<p>just use the following <span class="caps">CSS</span> rule:</p>
<p>.amp {<br />
font-family: &#8216;Hoefler Text&#8217;;<br />
font-style: italic;<br />
        }</p>
<p>The italic ampersand in Hoefler Text is&nbsp;gorgeous!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alenônimo</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1742</link>
		<dc:creator>Alenônimo</dc:creator>
		<pubDate>Sat, 12 Apr 2008 21:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1742</guid>
		<description>About the ligatures, why don't you create an option to search and replace some common ligatures like "Æ", "æ", "Œ" and "œ"?

You could even create an separate option for Unicode ligatures ("Ĳ", "ĳ", "ﬀ", "ﬁ", "ﬂ", "ﬃ", "ﬄ", "ﬅ" and "ﬆ"), even if they're barely supported. Well, we must start from somewhere.

You could give the option to exchange the "&#160;" entity to the actual non-breaking space character (Alt+0160 on Windows). Every character with an Alt code on Windows have a large degree of support.

And, finnaly, you could make suggestions to use with the CSS options. I really want to know what I could do with these classes but I'm not too creative.

Sorry for bothering you with so many suggestions. I really apreciate your plugin for WordPress.</description>
		<content:encoded><![CDATA[<p>About the ligatures, why don&#8217;t you create an option to search and replace some common ligatures like &#8220;Æ&#8221;, &#8220;æ&#8221;, &#8220;Œ&#8221; and &#8220;œ&#8221;?</p>
<p>You could even create an separate option for Unicode ligatures (&#8220;Ĳ&#8221;, &#8220;ĳ&#8221;, &#8220;ﬀ&#8221;, &#8220;ﬁ&#8221;, &#8220;ﬂ&#8221;, &#8220;ﬃ&#8221;, &#8220;ﬄ&#8221;, &#8220;ﬅ&#8221; and &#8220;ﬆ&#8221;), even if they&#8217;re barely supported. Well, we must start from somewhere.</p>
<p>You could give the option to exchange the &#8220;&nbsp;&#8221; entity to the actual non-breaking space character (Alt+0160 on Windows). Every character with an Alt code on Windows have a large degree of support.</p>
<p>And, finnaly, you could make suggestions to use with the <span class="caps">CSS</span> options. I really want to know what I could do with these classes but I&#8217;m not too creative.</p>
<p>Sorry for bothering you with so many suggestions. I really apreciate your plugin for&nbsp;WordPress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the hamstu &#187; Wordpress 2.5 and&#160;wp-typogrify</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1634</link>
		<dc:creator>the hamstu &#187; Wordpress 2.5 and&#160;wp-typogrify</dc:creator>
		<pubDate>Sun, 30 Mar 2008 02:55:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1634</guid>
		<description>[...] for wp-typogrify; there&#8217;s a bug that I&#8217;ve noticed (and been told about before) that I haven&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] for wp-typogrify; there&#8217;s a bug that I&#8217;ve noticed (and been told about before) that I haven&#8217;t&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dickson Fong &#187; Blog Archive &#187; A Website&#160;Is&#160;Born</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1621</link>
		<dc:creator>Dickson Fong &#187; Blog Archive &#187; A Website&#160;Is&#160;Born</dc:creator>
		<pubDate>Fri, 28 Mar 2008 19:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1621</guid>
		<description>[...] Hamish Macpherson’s&#160;wp-typogrify [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Hamish Macpherson’s&nbsp;wp-typogrify&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Upgrades and design&#160;tweaks at deanjrobinson.com</title>
		<link>http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1496</link>
		<dc:creator>Upgrades and design&#160;tweaks at deanjrobinson.com</dc:creator>
		<pubDate>Fri, 21 Mar 2008 11:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/2007/05/31/web-typography-just-got-better/#comment-1496</guid>
		<description>[...] also added a new plugin called wp-typogrify which as the name implies helps with the typography of blog entries and titles. The changes is make [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] also added a new plugin called wp-typogrify which as the name implies helps with the typography of blog entries and titles. The changes is make&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
