<?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: Lets use English in HTML</title>
	<atom:link href="http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/</link>
	<description>Thoughts on small business, the web industry and more, from Miles Burke, Author, Speaker, Entrepreneur &#38; Geek.</description>
	<pubDate>Tue, 06 Jan 2009 23:52:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Skor</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-662</link>
		<dc:creator>Skor</dc:creator>
		<pubDate>Tue, 11 Apr 2006 12:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-662</guid>
		<description>Use SPIP rather than HTML
and you will use FRENCH ! not english, not american :)</description>
		<content:encoded><![CDATA[<p>Use SPIP rather than HTML<br />
and you will use FRENCH ! not english, not american :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-650</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Sun, 09 Apr 2006 11:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-650</guid>
		<description>The solution is to not think of it as English. It's just syntax after all. Once you have programmed in more than one language, switching syntax becomes second nature. I'm told the same is true of non-monolingualists (although unfortunately I can't speak from experience).

It reminds me of my University days. When in a mathematics lecture, the square root of minus one was 'i'. When in an electronic engineering lecture, the same irrational number was 'j' (as 'i' was always used for electrical current). It's just the way it was (is) and you get used to it.

If you are still hung up on centre vs center/colour vs color, it just means you aren't coding enough in Java, PERL and Python.

As for the content you see in the rendered page - now that's a different story. It had better be the Queen's English because bad grammar makes me sic.</description>
		<content:encoded><![CDATA[<p>The solution is to not think of it as English. It&#8217;s just syntax after all. Once you have programmed in more than one language, switching syntax becomes second nature. I&#8217;m told the same is true of non-monolingualists (although unfortunately I can&#8217;t speak from experience).</p>
<p>It reminds me of my University days. When in a mathematics lecture, the square root of minus one was &#8216;i&#8217;. When in an electronic engineering lecture, the same irrational number was &#8216;j&#8217; (as &#8216;i&#8217; was always used for electrical current). It&#8217;s just the way it was (is) and you get used to it.</p>
<p>If you are still hung up on centre vs center/colour vs color, it just means you aren&#8217;t coding enough in Java, PERL and Python.</p>
<p>As for the content you see in the rendered page - now that&#8217;s a different story. It had better be the Queen&#8217;s English because bad grammar makes me sic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-449</link>
		<dc:creator>Grant</dc:creator>
		<pubDate>Sat, 25 Mar 2006 06:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-449</guid>
		<description>I propose an apache mod that parses our Australian css and outputs the US equivalent to the browser. I will name it mod_WhereTheBloodyHellIsMyStyleSheet

problem solved, thank you for listening.</description>
		<content:encoded><![CDATA[<p>I propose an apache mod that parses our Australian css and outputs the US equivalent to the browser. I will name it mod_WhereTheBloodyHellIsMyStyleSheet</p>
<p>problem solved, thank you for listening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miles</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-448</link>
		<dc:creator>Miles</dc:creator>
		<pubDate>Fri, 24 Mar 2006 04:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-448</guid>
		<description>Joetek - good point, I have revised accordingly. Apologies!</description>
		<content:encoded><![CDATA[<p>Joetek - good point, I have revised accordingly. Apologies!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joetek</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-447</link>
		<dc:creator>Joetek</dc:creator>
		<pubDate>Fri, 24 Mar 2006 04:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-447</guid>
		<description>I wholeheartedly agree!

Just keep in mind that while Canada does use Commonwealth English, we are also part of North America, so don't paint all of us North Americans with the same brush!</description>
		<content:encoded><![CDATA[<p>I wholeheartedly agree!</p>
<p>Just keep in mind that while Canada does use Commonwealth English, we are also part of North America, so don&#8217;t paint all of us North Americans with the same brush!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-446</link>
		<dc:creator>Nigel</dc:creator>
		<pubDate>Thu, 23 Mar 2006 18:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-446</guid>
		<description>It's about time someone brought this up - lets use international english, not its poor cousin, yankee english.</description>
		<content:encoded><![CDATA[<p>It&#8217;s about time someone brought this up - lets use international english, not its poor cousin, yankee english.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-445</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 23 Mar 2006 16:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-445</guid>
		<description>I've had that issue many times... and i know exactly what you mean. I think for me I just think of it as code/markup and divorce myself from it as "language" per se.

Although I am hoping nothing ever comes down to a "google-off" to decide which is right :)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had that issue many times&#8230; and i know exactly what you mean. I think for me I just think of it as code/markup and divorce myself from it as &#8220;language&#8221; per se.</p>
<p>Although I am hoping nothing ever comes down to a &#8220;google-off&#8221; to decide which is right :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PWills</title>
		<link>http://www.milesburke.com.au/blog/2006/03/23/lets-use-english-in-html/#comment-444</link>
		<dc:creator>PWills</dc:creator>
		<pubDate>Thu, 23 Mar 2006 13:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://miles.burke.id.au/blog/?p=43#comment-444</guid>
		<description>Interesting suggestion, but where does it end? Wouldn't you also need gris/grau/grigio not to mention the hundreds of double-byte Asian translations of the world 'grey'? 

I, for one, would rather have a global standard that is *wrong* than have no standard whatsoever. Imagine how difficult writing an ISO-standard SQL interpreter would be if you had to recognize SELECT or PRESCELTO or CHOICI or any of the thousands of ways to say 'select' around the world.</description>
		<content:encoded><![CDATA[<p>Interesting suggestion, but where does it end? Wouldn&#8217;t you also need gris/grau/grigio not to mention the hundreds of double-byte Asian translations of the world &#8216;grey&#8217;? </p>
<p>I, for one, would rather have a global standard that is *wrong* than have no standard whatsoever. Imagine how difficult writing an ISO-standard SQL interpreter would be if you had to recognize SELECT or PRESCELTO or CHOICI or any of the thousands of ways to say &#8217;select&#8217; around the world.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
