<?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: Even the Big Guys Get Validation Wrong</title>
	<atom:link href="http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/</link>
	<description>PHP Programming, Web Development, PHP Advocacy and PHP Best Practices.</description>
	<lastBuildDate>Sat, 11 Feb 2012 14:53:56 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James Benson</title>
		<link>http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-83909</link>
		<dc:creator>James Benson</dc:creator>
		<pubDate>Wed, 02 Jul 2008 01:32:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-83909</guid>
		<description>Most the sites I&#039;ve seen do not replace spaces, how hard can it be.</description>
		<content:encoded><![CDATA[<p>Most the sites I&#8217;ve seen do not replace spaces, how hard can it be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-81450</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 01 May 2007 17:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-81450</guid>
		<description>I just type it in slowly and dont put in spaces cause of that error. 

Its one of those things, dont get too caught up in not making errors. If you do go back and correct it, but check your work over slowly the first time.</description>
		<content:encoded><![CDATA[<p>I just type it in slowly and dont put in spaces cause of that error. </p>
<p>Its one of those things, dont get too caught up in not making errors. If you do go back and correct it, but check your work over slowly the first time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enric Naval</title>
		<link>http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-652</link>
		<dc:creator>Enric Naval</dc:creator>
		<pubDate>Mon, 08 Nov 2004 17:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-652</guid>
		<description>Ejem, let&#039;s try a smaller text size.

&lt;font size=&quot;1&quot;&gt;Example: XXXXXXXXXXXX (all numbers, no spaces)&lt;/font&gt;</description>
		<content:encoded><![CDATA[<p>Ejem, let&#8217;s try a smaller text size.</p>
<p><font size="1">Example: XXXXXXXXXXXX (all numbers, no spaces)</font></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enric Naval</title>
		<link>http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-651</link>
		<dc:creator>Enric Naval</dc:creator>
		<pubDate>Mon, 08 Nov 2004 17:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.procata.com/blog/archives/2004/05/13/even-the-big-guys-get-validation-wrong/#comment-651</guid>
		<description>This can be solved by puting a small example entry besides the text area. The users would see a text like:
&lt;em&gt;&lt;font size=&quot;7&quot;&gt;Example: XXXXXXXXXXXX (all numbers, no spaces)[&lt;/font&gt;&lt;/em&gt;
When users encounter the problem, they will read the small example text and remove the spaces to make their entry as similar to the example as posible.

This is many times easier than checking and correcting every single possible way a user can enter the data (users can be very imaginative when it comes to mangling input data].</description>
		<content:encoded><![CDATA[<p>This can be solved by puting a small example entry besides the text area. The users would see a text like:<br />
<em><font size="7">Example: XXXXXXXXXXXX (all numbers, no spaces)[</font></em><br />
When users encounter the problem, they will read the small example text and remove the spaces to make their entry as similar to the example as posible.</p>
<p>This is many times easier than checking and correcting every single possible way a user can enter the data (users can be very imaginative when it comes to mangling input data].</p>
]]></content:encoded>
	</item>
</channel>
</rss>

