<?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: A Better Acronym Replacer for WordPress</title>
	<atom:link href="http://phnk.com/varia/better-wordpress-acronyms/feed/" rel="self" type="application/rss+xml" />
	<link>http://phnk.com/varia/better-wordpress-acronyms/</link>
	<description></description>
	<lastBuildDate>Sun, 31 Jan 2010 15:39:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: François</title>
		<link>http://phnk.com/varia/better-wordpress-acronyms/comment-page-1/#comment-201</link>
		<dc:creator>François</dc:creator>
		<pubDate>Thu, 18 May 2006 07:21:20 +0000</pubDate>
		<guid isPermaLink="false">http://phnk.com/blog/technologie/rt/#comment-201</guid>
		<description>&lt;p&gt;It&#039;s a sound argument that we should be using at least two different tags for acronyms and abbreviations (though I tend to disagree: HTML can be considered an acronym to a large extent).&lt;/p&gt;

&lt;p&gt;Yet Ubernyms would be jumping to a higher level of sophistication: I am not sure I need to get down that road, I would rather go for the Wikipedia linkage. I will have to consider both in the future (I guess that I will opt, in the end, for Ubernyms, because I believe we are both part of that kind of überperfectionists who use complicated plugins for stuff that a vast majority of people do not give a straight damn about).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s a sound argument that we should be using at least two different tags for acronyms and abbreviations (though I tend to disagree: <acronym title="HyperText Markup Language">HTML</acronym> can be considered an acronym to a large extent).</p>

<p>Yet Ubernyms would be jumping to a higher level of sophistication: I am not sure I need to get down that road, I would rather go for the Wikipedia linkage. I will have to consider both in the future (I guess that I will opt, in the end, for Ubernyms, because I believe we are both part of that kind of überperfectionists who use complicated plugins for stuff that a vast majority of people do not give a straight damn about).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Joel "Jaykul" Bennett</title>
		<link>http://phnk.com/varia/better-wordpress-acronyms/comment-page-1/#comment-200</link>
		<dc:creator>Joel "Jaykul" Bennett</dc:creator>
		<pubDate>Thu, 18 May 2006 04:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://phnk.com/blog/technologie/rt/#comment-200</guid>
		<description>&lt;p&gt;You know, even if all you&#039;re using it for is abbreviations, you&#039;re better off with Ubernyms because it would use the &lt;strong&gt;right&lt;/strong&gt; tag instead of the acronym tag for things like &quot;HTML&quot; that aren&#039;t actually acronyms ;)  That&#039;s actually why I finally released it: I added the ability to say that some acronyms are obscure (to your readers), and you want to place the full text in the article (in parentheses) the first time you use it... which is the &lt;strong&gt;correct&lt;/strong&gt; way to do it.&lt;/p&gt;

&lt;p&gt;I realized that I&#039;m tired of people arguing about &lt;code&gt;ABBR&lt;/code&gt; vs &lt;code&gt;ACRONYM&lt;/code&gt; (because &lt;code&gt;ABBR&lt;/code&gt; doesn&#039;t show up highlighted in IE) when they &lt;strong&gt;should&lt;/strong&gt; just write it as they would on paper, and then add a tag to help the computers understand what&#039;s going on (and read it correctly to blind people).&lt;/p&gt;

&lt;p&gt;in English, and – apart from all the semantics of adding tags for the computer to read.&lt;/p&gt;

&lt;p&gt;Anyway, feel free to keep using and improving the old one of course!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You know, even if all you&#8217;re using it for is abbreviations, you&#8217;re better off with Ubernyms because it would use the <strong>right</strong> tag instead of the acronym tag for things like &#8220;<acronym title="HyperText Markup Language">HTML</acronym>&#8221; that aren&#8217;t actually acronyms ;)  That&#8217;s actually why I finally released it: I added the ability to say that some acronyms are obscure (to your readers), and you want to place the full text in the article (in parentheses) the first time you use it&#8230; which is the <strong>correct</strong> way to do it.</p>

<p>I realized that I&#8217;m tired of people arguing about <code>ABBR</code> vs <code>ACRONYM</code> (because <code>ABBR</code> doesn&#8217;t show up highlighted in <acronym title="Internet Explorer">IE</acronym>) when they <strong>should</strong> just write it as they would on paper, and then add a tag to help the computers understand what&#8217;s going on (and read it correctly to blind people).</p>

<p>in English, and – apart from all the semantics of adding tags for the computer to read.</p>

<p>Anyway, feel free to keep using and improving the old one of course!</p>]]></content:encoded>
	</item>
</channel>
</rss>
