<?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 merging and moving</title>
	<atom:link href="http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/</link>
	<description>design and programming hybridized</description>
	<pubDate>Mon, 06 Sep 2010 18:56:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: wp‐​Typography 1.0 beta 1 &#8226; KINGdesk</title>
		<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/#comment-11158</link>
		<dc:creator>wp‐​Typography 1.0 beta 1 &#8226; KINGdesk</dc:creator>
		<pubDate>Sat, 04 Jul 2009 03:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/?p=89#comment-11158</guid>
		<description>[...] is the merger and expan­sion of the wp‐​Typogrify and wp‐​Hyphenate plu­g­ins and Smar­ty­Pants func­tion­al­ity. It is now a [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] is the merger and expan­sion of the wp‐​Typogrify and wp‐​Hyphenate plu­g­ins and Smar­ty­Pants func­tion­al­ity. It is now a&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JUICEDaniel</title>
		<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/#comment-10262</link>
		<dc:creator>JUICEDaniel</dc:creator>
		<pubDate>Sat, 23 May 2009 18:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/?p=89#comment-10262</guid>
		<description>Nice plan to combine these two plugins - if they work with WP 2.7.1 then. How far are you? Any updates? I seek desperately for a typo-plugin working fine with WP 2.7.1!!! (And I bet there are thousand others out there, waiting, too (some of them might not know yet, that they're waiting... but as soon as the plugin is released and works: they know!) - go go go :)</description>
		<content:encoded><![CDATA[<p>Nice plan to combine these two plugins - if they work with <span class="caps">WP</span> 2.7.1 then. How far are you? Any updates? I seek desperately for a typo-plugin working fine with <span class="caps">WP</span> 2.7.1!!! (And I bet there are thousand others out there, waiting, too (some of them might not know yet, that they&#8217;re waiting&#8230; but as soon as the plugin is released and works: they know!) - go go go&nbsp;:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel</title>
		<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/#comment-8015</link>
		<dc:creator>Nigel</dc:creator>
		<pubDate>Sun, 01 Mar 2009 20:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/?p=89#comment-8015</guid>
		<description>I'm having an issue where wp-typogrify seems to interfere with image alignment and display of captions.

See http://wordpress.org/support/topic/243014?replies=9

I've tested on a clean install of WordPress 2.7. Enabling only the wp-typogrify plugin seems to prevent image alignment in blog posts from working. Disabling it brings back the expected wordpress behaviour. Is this a known issue?</description>
		<content:encoded><![CDATA[<p>I&#8217;m having an issue where wp-typogrify seems to interfere with image alignment and display of captions.</p>
<p>See <a href="http://wordpress.org/support/topic/243014?replies=9" rel="nofollow">http://wordpress.org/support/topic/243014?replies=9</a></p>
<p>I&#8217;ve tested on a clean install of WordPress 2.7. Enabling only the wp-typogrify plugin seems to prevent image alignment in blog posts from working. Disabling it brings back the expected wordpress behaviour. Is this a known&nbsp;issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technocrank</title>
		<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/#comment-7999</link>
		<dc:creator>Technocrank</dc:creator>
		<pubDate>Sat, 28 Feb 2009 14:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/?p=89#comment-7999</guid>
		<description>&lt;strong&gt;WP-Typogrify Wordpress Plugin: Widows...&lt;/strong&gt;

Typogrify 1.6
Word­press 2.7.1
The Typogrify plugin seems to wipe out the con­tent of some single post pages when the widow pre­ven­tion option is activated.  I don&#8217;t have the patience right now to trou­bleshoot it, but the wp-​Hyphenate...</description>
		<content:encoded><![CDATA[<p><strong><span class="caps">WP</span>-Typogrify Wordpress Plugin: Widows&#8230;</strong></p>
<p>Typogrify 1.6<br />
Word­press 2.7.1<br />
The Typogrify plugin seems to wipe out the con­tent of some single post pages when the widow pre­ven­tion option is activated.  I don&#8217;t have the patience right now to trou­bleshoot it, but the&nbsp;wp-​Hyphenate&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Wiebe</title>
		<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/#comment-7994</link>
		<dc:creator>Matt Wiebe</dc:creator>
		<pubDate>Fri, 27 Feb 2009 23:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/?p=89#comment-7994</guid>
		<description>That sounds like fantastic news. A one-stop-shop for typographic goodness.</description>
		<content:encoded><![CDATA[<p>That sounds like fantastic news. A one-stop-shop for typographic&nbsp;goodness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/#comment-7942</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Sun, 22 Feb 2009 14:18:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hamstu.com/?p=89#comment-7942</guid>
		<description>Yes I am. And I'm happy to hear you're maintaining it.

I have a problem with &#60;samp&#62; though. wp-typogrify would transform quotes, while it wouldn't do that with &#60;code&#62; and &#60;pre&#62; elements, i guess you could simply modify the regex, so that &#60;samp&#62;-elements stay intact.

Thank you so much!</description>
		<content:encoded><![CDATA[<p>Yes I am. And I&#8217;m happy to hear you&#8217;re maintaining it.</p>
<p>I have a problem with &lt;samp&gt; though. wp-typogrify would transform quotes, while it wouldn&#8217;t do that with &lt;code&gt; and &lt;pre&gt; elements, i guess you could simply modify the regex, so that &lt;samp&gt;-elements stay intact.</p>
<p>Thank you so&nbsp;much!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
