<?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 for Qodo</title>
	<atom:link href="http://www.qodo.co.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.qodo.co.uk</link>
	<description>Freelance Web Designer &#38; Developer, Stewart Orr</description>
	<lastBuildDate>Thu, 25 Feb 2010 04:12:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Re-introducing @font-face CSS rules by Richard Fink</title>
		<link>http://www.qodo.co.uk/blog/re-introducing-font-face-css-rules/comment-page-1/#comment-934</link>
		<dc:creator>Richard Fink</dc:creator>
		<pubDate>Thu, 25 Feb 2010 04:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.qodo.co.uk/blog/re-introducing-font-face-css-rules/#comment-934</guid>
		<description>If you&#039;re going to be using @font-face web fonts check out this new free tool:
&lt;a href=&quot;http://eotfast.com&quot; rel=&quot;nofollow&quot;&gt;EOTFAST&lt;/a&gt;
EOTFAST is a utility for creating natively compressed EOT files for use with any domain.
Convert once, use on any site. Savings in file size typically range from 45% to 70%.
It&#039;s fair to say that other conversions utilities like Microsoft WEFT or ttf2eot are now obsolete.
A great screen font like Droid Serif starts out at 169kb as a TTF with the full character set but as an EOTFAST file it weighs in at only 80kb. With still the full character set. Compression is lossless.
The documentation contains information for designers looking to prepare fonts for use on the web.
The download package also contains a HTML &quot;EOT File Integrity Test&quot; page and a helpful &quot;fallback&quot; test font. 
&lt;a href=&quot;http://eotfast.com&quot; rel=&quot;nofollow&quot;&gt;EOTFAST&lt;/a&gt; is a must-have for anyone looking to use @font-face web fonts today.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re going to be using @font-face web fonts check out this new free tool:<br />
<a href="http://eotfast.com" rel="nofollow">EOTFAST</a><br />
EOTFAST is a utility for creating natively compressed EOT files for use with any domain.<br />
Convert once, use on any site. Savings in file size typically range from 45% to 70%.<br />
It&#8217;s fair to say that other conversions utilities like Microsoft WEFT or ttf2eot are now obsolete.<br />
A great screen font like Droid Serif starts out at 169kb as a TTF with the full character set but as an EOTFAST file it weighs in at only 80kb. With still the full character set. Compression is lossless.<br />
The documentation contains information for designers looking to prepare fonts for use on the web.<br />
The download package also contains a HTML &#8220;EOT File Integrity Test&#8221; page and a helpful &#8220;fallback&#8221; test font.<br />
<a href="http://eotfast.com" rel="nofollow">EOTFAST</a> is a must-have for anyone looking to use @font-face web fonts today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Re-introducing @font-face CSS rules by Don&#8217;t miss out! &#171; The Paper Cow</title>
		<link>http://www.qodo.co.uk/blog/re-introducing-font-face-css-rules/comment-page-1/#comment-906</link>
		<dc:creator>Don&#8217;t miss out! &#171; The Paper Cow</dc:creator>
		<pubDate>Tue, 23 Feb 2010 06:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.qodo.co.uk/blog/re-introducing-font-face-css-rules/#comment-906</guid>
		<description>[...] The coding uses an @font-face command, which I learned from my friend, Neil, and where you can find more about here. [...]</description>
		<content:encoded><![CDATA[<p>[...] The coding uses an @font-face command, which I learned from my friend, Neil, and where you can find more about here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JavaScript: Restrict keyboard character input by Paul Gardner</title>
		<link>http://www.qodo.co.uk/blog/javascript-restrict-keyboard-character-input/comment-page-1/#comment-606</link>
		<dc:creator>Paul Gardner</dc:creator>
		<pubDate>Wed, 03 Feb 2010 12:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.qodo.co.uk/?p=153#comment-606</guid>
		<description>I give up.

Came across http://www.quirksmode.org/js/keys.html which shows that reliably detecting key/charCodes across all browsers and OS is a minefield and do not want to risk people not being able to use my forms. 

Will revert to server-side validation for non-allowed chars.

I was getting somewhere when I realised that chars 36, 37, 38, 39 and 40 were duplicated as the arrow and home keys and was checking for existence of shift key, but FireFox and IE have different behaviours and that&#039;s just on Windows.

Hey ho, nice idea .. anyone know one of the twitter developers really well as they seem to have this licked?!?

Paul.</description>
		<content:encoded><![CDATA[<p>I give up.</p>
<p>Came across <a href="http://www.quirksmode.org/js/keys.html" rel="nofollow">http://www.quirksmode.org/js/keys.html</a> which shows that reliably detecting key/charCodes across all browsers and OS is a minefield and do not want to risk people not being able to use my forms. </p>
<p>Will revert to server-side validation for non-allowed chars.</p>
<p>I was getting somewhere when I realised that chars 36, 37, 38, 39 and 40 were duplicated as the arrow and home keys and was checking for existence of shift key, but FireFox and IE have different behaviours and that&#8217;s just on Windows.</p>
<p>Hey ho, nice idea .. anyone know one of the twitter developers really well as they seem to have this licked?!?</p>
<p>Paul.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JavaScript: Restrict keyboard character input by Stewart</title>
		<link>http://www.qodo.co.uk/blog/javascript-restrict-keyboard-character-input/comment-page-1/#comment-605</link>
		<dc:creator>Stewart</dc:creator>
		<pubDate>Wed, 03 Feb 2010 11:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.qodo.co.uk/?p=153#comment-605</guid>
		<description>Hi Paul. A few people have said something similar to this. You could change the line to:

&lt;pre&gt;&lt;code&gt;if (!e.ctrlKey &amp;&amp; code!=9 &amp;&amp; code!=8 &amp;&amp; (code!=39 &#124;&#124; (code==39 &amp;&amp; character==&quot;&#039;&quot;)) &amp;&amp; code!=40) {&lt;/code&gt;&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Hi Paul. A few people have said something similar to this. You could change the line to:</p>
<pre><code>if (!e.ctrlKey &#038;&#038; code!=9 &#038;&#038; code!=8 &#038;&#038; (code!=39 || (code==39 &#038;&#038; character=="'")) &#038;&#038; code!=40) {</code></pre>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JavaScript: Restrict keyboard character input by Paul Gardner</title>
		<link>http://www.qodo.co.uk/blog/javascript-restrict-keyboard-character-input/comment-page-1/#comment-604</link>
		<dc:creator>Paul Gardner</dc:creator>
		<pubDate>Wed, 03 Feb 2010 11:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.qodo.co.uk/?p=153#comment-604</guid>
		<description>Great script .. I&#039;m tryig to use it to replicate the username field treatment on twitter so it only allows 0-9 A-Z a-z and underscore.

I am using /[0-9A-Za-z_]/g but it&#039;s also allowing the chars $ % &amp; (. 

Your example alpha script also allows these extra chars.

Any ideas anyone?</description>
		<content:encoded><![CDATA[<p>Great script .. I&#8217;m tryig to use it to replicate the username field treatment on twitter so it only allows 0-9 A-Z a-z and underscore.</p>
<p>I am using /[0-9A-Za-z_]/g but it&#8217;s also allowing the chars $ % &amp; (. </p>
<p>Your example alpha script also allows these extra chars.</p>
<p>Any ideas anyone?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
