<?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: Advanced Spell Checker For WordPress</title>
	<atom:link href="http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/</link>
	<description>A blog about web development, software business, and WordPress</description>
	<lastBuildDate>Tue, 22 May 2012 04:00:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: 11 ways to maximize your blog traffic in 2011 &#124; Novel Publicity</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-165826</link>
		<dc:creator>11 ways to maximize your blog traffic in 2011 &#124; Novel Publicity</dc:creator>
		<pubDate>Wed, 02 Feb 2011 13:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-165826</guid>
		<description>[...] Use the advanced spellchecker—this feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent.  Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly?  WordPress’s spellchecker can pick up on this type of usage error.  You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice, and redundant phrases. . [...]</description>
		<content:encoded><![CDATA[<p>[...] Use the advanced spellchecker—this feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent.  Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly?  WordPress’s spellchecker can pick up on this type of usage error.  You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice, and redundant phrases. . [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest Post by Emlyn Chand &#8211; 11 Steps to Better Blogging &#124; My Pajama Days</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-163738</link>
		<dc:creator>Guest Post by Emlyn Chand &#8211; 11 Steps to Better Blogging &#124; My Pajama Days</dc:creator>
		<pubDate>Mon, 10 Jan 2011 06:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-163738</guid>
		<description>[...] Use the advanced spellchecker—this feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent.  Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly?  WordPress’s spellchecker can pick up on this type of usage error.  You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice, and redundant phrases. [...]</description>
		<content:encoded><![CDATA[<p>[...] Use the advanced spellchecker—this feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent.  Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly?  WordPress’s spellchecker can pick up on this type of usage error.  You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice, and redundant phrases. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 11 steps for getting the most out of your writing blog in 2011 &#124; Writing to Success</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-159106</link>
		<dc:creator>11 steps for getting the most out of your writing blog in 2011 &#124; Writing to Success</dc:creator>
		<pubDate>Tue, 04 Jan 2011 10:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-159106</guid>
		<description>[...] Use the advanced spellchecker—This feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent. Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly? WordPress’s spellchecker can pick up on this type of usage error. You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice and redundant phrases. [...]</description>
		<content:encoded><![CDATA[<p>[...] Use the advanced spellchecker—This feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent. Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly? WordPress’s spellchecker can pick up on this type of usage error. You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice and redundant phrases. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 11 steps for getting the most out of your writing blog in 2011 &#171; The Ambitious Ambigue</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-158538</link>
		<dc:creator>11 steps for getting the most out of your writing blog in 2011 &#171; The Ambitious Ambigue</dc:creator>
		<pubDate>Mon, 03 Jan 2011 16:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-158538</guid>
		<description>[...] Use the advanced spellchecker—this feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent.  Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly?  WordPress’s spellchecker can pick up on this type of usage error.  You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice, and redundant phrases. . [...]</description>
		<content:encoded><![CDATA[<p>[...] Use the advanced spellchecker—this feature is one of the greatest things to ever happen to me as a writer—I’m not exaggerating! The WordPress.com advanced spelling and grammar checker is a God-sent.  Even though Microsoft Word’s standard spellchecker is a good thing to have, aren’t you sometimes frustrated when it doesn’t pick up a usage mistake (like “their,” “they’re” or “there”) just because the word is technically spelled correctly?  WordPress’s spellchecker can pick up on this type of usage error.  You can also customize its options to check for biased language, clichés, complex phrases, diacritical marks, double negatives, hidden verbs, jargon, passive voice, and redundant phrases. . [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: One year of After the Deadline &#171; After the Deadline</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-50693</link>
		<dc:creator>One year of After the Deadline &#171; After the Deadline</dc:creator>
		<pubDate>Fri, 04 Jun 2010 16:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-50693</guid>
		<description>[...] On 1 Jun 09, I launched After the Deadline. The first review of After the Deadline (AtD) came from w-shadow.com. There were also discussions on CMSReport.com and Hacker [...]</description>
		<content:encoded><![CDATA[<p>[...] On 1 Jun 09, I launched After the Deadline. The first review of After the Deadline (AtD) came from w-shadow.com. There were also discussions on CMSReport.com and Hacker [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raphael Mudge</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-30423</link>
		<dc:creator>Raphael Mudge</dc:creator>
		<pubDate>Tue, 02 Jun 2009 16:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-30423</guid>
		<description>Oops, this the perfectionist scientist in me who can&#039;t edit comments: the numbers are 0.005 or 0.5%, 0.0011 or 0.11%, 0.0029 or 0.29%.  I apologize for the confusion I may have caused leaving the errant % in there.</description>
		<content:encoded><![CDATA[<p>Oops, this the perfectionist scientist in me who can&#8217;t edit comments: the numbers are 0.005 or 0.5%, 0.0011 or 0.11%, 0.0029 or 0.29%.  I apologize for the confusion I may have caused leaving the errant % in there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raphael Mudge</title>
		<link>http://w-shadow.com/blog/2009/06/02/advanced-spell-checker-for-wordpress/comment-page-1/#comment-30422</link>
		<dc:creator>Raphael Mudge</dc:creator>
		<pubDate>Tue, 02 Jun 2009 16:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://w-shadow.com/?p=1138#comment-30422</guid>
		<description>Thanks for the write up.  Without any biasing I&#039;m able to detect misused words with 90% accuracy.  Unfortunately without any biasing I also flag correctly used words as misused.  This especially becomes a problem because folks are more likely to use a word correctly than incorrectly.  

So what I&#039;ve one is identified words the statistical model doesn&#039;t  work well for (it&#039;s/its, a/an, there/their, etc), moved them away from the misused word list, and created grammar rules for them.

This has given me some wiggle room to cut my biasing down.  I&#039;m aiming for a 0.0050 false positive rate--it&#039;s at 0.0011 and 0.0029% in my tests now.  Once I change this balance you&#039;ll notice the misused word detection is more accurate.  

What makes this problem challenging is for some words (depending on the context) either word could feasibly be correct.  The solution is to look at more context but the more context I choose to use the more danger I have of data sparseness leading to more false positives and less coverage of how the words are actually used.  It&#039;s an interesting problem.  

What is nice (from my perspective) is where one tool falls short, I have another tool I can use to make up the difference (such as the grammar checker).</description>
		<content:encoded><![CDATA[<p>Thanks for the write up.  Without any biasing I&#8217;m able to detect misused words with 90% accuracy.  Unfortunately without any biasing I also flag correctly used words as misused.  This especially becomes a problem because folks are more likely to use a word correctly than incorrectly.  </p>
<p>So what I&#8217;ve one is identified words the statistical model doesn&#8217;t  work well for (it&#8217;s/its, a/an, there/their, etc), moved them away from the misused word list, and created grammar rules for them.</p>
<p>This has given me some wiggle room to cut my biasing down.  I&#8217;m aiming for a 0.0050 false positive rate&#8211;it&#8217;s at 0.0011 and 0.0029% in my tests now.  Once I change this balance you&#8217;ll notice the misused word detection is more accurate.  </p>
<p>What makes this problem challenging is for some words (depending on the context) either word could feasibly be correct.  The solution is to look at more context but the more context I choose to use the more danger I have of data sparseness leading to more false positives and less coverage of how the words are actually used.  It&#8217;s an interesting problem.  </p>
<p>What is nice (from my perspective) is where one tool falls short, I have another tool I can use to make up the difference (such as the grammar checker).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

