<?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: www-less</title>
	<atom:link href="http://blog.javia.org/www-less/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.javia.org/www-less/</link>
	<description>Android apps</description>
	<lastBuildDate>Fri, 11 Nov 2011 12:16:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: mihai</title>
		<link>http://blog.javia.org/www-less/comment-page-1/#comment-6</link>
		<dc:creator>mihai</dc:creator>
		<pubDate>Tue, 13 Jun 2006 10:30:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frumos.com/?p=6#comment-6</guid>
		<description>On my mobile phone application I wanted to indicate the  app website&#039;s URL. As you say, I had the choice between:
http://menstral.net/ and  www.menstral.net

The www-variant is 4 characters shorter than the http:// form, and the lenght is just more important on the small mobile display. The http:// URL wouldn&#039;t even fit on a single line.

So this is one useful aspect of &quot;www.&quot;. That&#039;s why I propose to have &quot;www.name.com&quot; redirecting to &quot;name.com&quot;, rather than reject &quot;www.name.com&quot; altogether.</description>
		<content:encoded><![CDATA[<p>On my mobile phone application I wanted to indicate the  app website&#8217;s URL. As you say, I had the choice between:<br />
<a href="http://menstral.net/" rel="nofollow">http://menstral.net/</a> and  <a href="http://www.menstral.net" rel="nofollow">http://www.menstral.net</a></p>
<p>The www-variant is 4 characters shorter than the http:// form, and the lenght is just more important on the small mobile display. The http:// URL wouldn&#8217;t even fit on a single line.</p>
<p>So this is one useful aspect of &#8220;www.&#8221;. That&#8217;s why I propose to have &#8220;www.name.com&#8221; redirecting to &#8220;name.com&#8221;, rather than reject &#8220;www.name.com&#8221; altogether.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Razvan Florian</title>
		<link>http://blog.javia.org/www-less/comment-page-1/#comment-5</link>
		<dc:creator>Razvan Florian</dc:creator>
		<pubDate>Tue, 13 Jun 2006 08:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frumos.com/?p=6#comment-5</guid>
		<description>Using the www prefix in print (e.g., advertising material) helps indicating that you refer to a website. This is especially true for new or uncommon TLDs (e.g., .info, .eu, etc.). Otherwise you have to say http://name.com, which is more awkward than using www.</description>
		<content:encoded><![CDATA[<p>Using the www prefix in print (e.g., advertising material) helps indicating that you refer to a website. This is especially true for new or uncommon TLDs (e.g., .info, .eu, etc.). Otherwise you have to say <a href="http://name.com" rel="nofollow">http://name.com</a>, which is more awkward than using www.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

