<?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: Complicated solution to Mail.app&#8217;s broken hyperlinks</title>
	<atom:link href="http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/</link>
	<description>Tips and add-ons to make Apple Mail / Mail.app even better</description>
	<lastBuildDate>Mon, 21 Nov 2011 18:23:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bill Miller</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-125977</link>
		<dc:creator>Bill Miller</dc:creator>
		<pubDate>Mon, 09 Apr 2007 20:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-125977</guid>
		<description>The opening paragraph ought to be corrected. It&#039;s not Mail.apps fault that other clients are brain-dead. You&#039;re pointing the finger the wrong direction, Hawk Wings.</description>
		<content:encoded><![CDATA[<p>The opening paragraph ought to be corrected. It&#8217;s not Mail.apps fault that other clients are brain-dead. You&#8217;re pointing the finger the wrong direction, Hawk Wings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-113864</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 26 Mar 2007 12:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-113864</guid>
		<description>&quot;I wish Apple would fix this&quot;

It is not they, nor others who are also following RFC3676, who need to fix their implementation: it isn&#039;t broken.

The standard format=flowed, as described in RFC2646, exists so that text can be easily re-flowed whatever the size of the display. It was originally a suggestion made by the Eudora people--and that&#039;s not surprising since Qualcomm had a hand in cellphones:

http://joeclark.org/ffaq.html

There is a reason for the change, that RFC376 brings, too:

&quot;The newer technique, suitable for use even with languages/coded character sets in which the ASCII space character is rare or not used, creates a soft line break by inserting a SP CRLF sequence. When this technique is used, the DelSp parameter MUST be used and MUST be set to &quot;yes&quot;.&quot;

http://www.ietf.org/rfc/rfc3676.txt

Apple and Opera seem to have no problems doing as suggested.

Neither does Mulberry:

http://trac.mulberrymail.com/mulberry/ticket/5

KDE&#039;s Kontact has it marked as a bug to fix:

http://bugs.kde.org/show_bug.cgi?id=92591

What are software developers to say? &quot;Hard luck if your language is one in which in which &#039;the ASCII space character is rare or not used&#039;, because we&#039;re going to ignore the means that have been devised specifically to help you.&quot;?</description>
		<content:encoded><![CDATA[<p>&#8220;I wish Apple would fix this&#8221;</p>
<p>It is not they, nor others who are also following RFC3676, who need to fix their implementation: it isn&#8217;t broken.</p>
<p>The standard format=flowed, as described in RFC2646, exists so that text can be easily re-flowed whatever the size of the display. It was originally a suggestion made by the Eudora people&#8211;and that&#8217;s not surprising since Qualcomm had a hand in cellphones:</p>
<p><a href="http://joeclark.org/ffaq.html" rel="nofollow">http://joeclark.org/ffaq.html</a></p>
<p>There is a reason for the change, that RFC376 brings, too:</p>
<p>&#8220;The newer technique, suitable for use even with languages/coded character sets in which the ASCII space character is rare or not used, creates a soft line break by inserting a SP CRLF sequence. When this technique is used, the DelSp parameter MUST be used and MUST be set to &#8220;yes&#8221;.&#8221;</p>
<p><a href="http://www.ietf.org/rfc/rfc3676.txt" rel="nofollow">http://www.ietf.org/rfc/rfc3676.txt</a></p>
<p>Apple and Opera seem to have no problems doing as suggested.</p>
<p>Neither does Mulberry:</p>
<p><a href="http://trac.mulberrymail.com/mulberry/ticket/5" rel="nofollow">http://trac.mulberrymail.com/mulberry/ticket/5</a></p>
<p>KDE&#8217;s Kontact has it marked as a bug to fix:</p>
<p><a href="http://bugs.kde.org/show_bug.cgi?id=92591" rel="nofollow">http://bugs.kde.org/show_bug.cgi?id=92591</a></p>
<p>What are software developers to say? &#8220;Hard luck if your language is one in which in which &#8216;the ASCII space character is rare or not used&#8217;, because we&#8217;re going to ignore the means that have been devised specifically to help you.&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Peter Reed</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-113858</link>
		<dc:creator>Mike Peter Reed</dc:creator>
		<pubDate>Mon, 26 Mar 2007 11:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-113858</guid>
		<description>@Clair - that&#039;s exactly what I was trying to say! I just couldn&#039;t get those symbols to reproduce in the comments field! Thanks for a glimmer of sanity!</description>
		<content:encoded><![CDATA[<p>@Clair &#8211; that&#8217;s exactly what I was trying to say! I just couldn&#8217;t get those symbols to reproduce in the comments field! Thanks for a glimmer of sanity!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Warne</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-113852</link>
		<dc:creator>Dan Warne</dc:creator>
		<pubDate>Mon, 26 Mar 2007 11:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-113852</guid>
		<description>I wish Apple would fix this -- even if it means breaking RFC compliance. Simply digging in their heels and waiting will -not- magically convince Microsoft to implement it in Outlook, Outlook Express, or Windows Mail, which, let&#039;s face it, are used by the vast majority of people Mac users are emailing. 

In fact I&#039;m jack of the fact that URLs break so much all time time in all mail clients. Why is that Microsoft can take six years to create a new version of Windows and totally redesign the user interface of Office 2007 and STILL NOT BE ABLE TO HANDLE BROKEN URLS ELEGANTLY!?

How can we put man on the moon, hook up massive computing grids and create Pixar movies, and yet still not be able to solve one of the most basic problems in computing: broken URLs in emails? It&#039;s BLOODY ANNOYING!</description>
		<content:encoded><![CDATA[<p>I wish Apple would fix this &#8212; even if it means breaking RFC compliance. Simply digging in their heels and waiting will -not- magically convince Microsoft to implement it in Outlook, Outlook Express, or Windows Mail, which, let&#8217;s face it, are used by the vast majority of people Mac users are emailing. </p>
<p>In fact I&#8217;m jack of the fact that URLs break so much all time time in all mail clients. Why is that Microsoft can take six years to create a new version of Windows and totally redesign the user interface of Office 2007 and STILL NOT BE ABLE TO HANDLE BROKEN URLS ELEGANTLY!?</p>
<p>How can we put man on the moon, hook up massive computing grids and create Pixar movies, and yet still not be able to solve one of the most basic problems in computing: broken URLs in emails? It&#8217;s BLOODY ANNOYING!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clair</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-112598</link>
		<dc:creator>Clair</dc:creator>
		<pubDate>Sat, 24 Mar 2007 21:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-112598</guid>
		<description>What&#039;s wrong with using &lt; and &gt; symbols around the links? That&#039;s always worked for me.</description>
		<content:encoded><![CDATA[<p>What&#8217;s wrong with using &lt; and &gt; symbols around the links? That&#8217;s always worked for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-112358</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 24 Mar 2007 13:45:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-112358</guid>
		<description>&quot;The Delsp option used by Mail is in the RFC, so Apple is following the standard. The problem is that no one else is.&quot;

That&#039;s not true. Cyrus Daboo has fixed Mulberry Mail so that it now follows the standards. Opera Mail certainly does as well. So credit where it&#039;s due. It&#039;s possible that others do, too, but I don&#039;t know the capabilities of everything out there.

Of course, if we are waiting on *Microsoft* to fix its software, we may be in for a very long wait. IE is a case in point. It can now--finally--deal with alpha-transparency in PNGs, and how long has that taken? But its CSS-handling, and much else besides, is still *years* out-of-date.</description>
		<content:encoded><![CDATA[<p>&#8220;The Delsp option used by Mail is in the RFC, so Apple is following the standard. The problem is that no one else is.&#8221;</p>
<p>That&#8217;s not true. Cyrus Daboo has fixed Mulberry Mail so that it now follows the standards. Opera Mail certainly does as well. So credit where it&#8217;s due. It&#8217;s possible that others do, too, but I don&#8217;t know the capabilities of everything out there.</p>
<p>Of course, if we are waiting on *Microsoft* to fix its software, we may be in for a very long wait. IE is a case in point. It can now&#8211;finally&#8211;deal with alpha-transparency in PNGs, and how long has that taken? But its CSS-handling, and much else besides, is still *years* out-of-date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Gaden</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-112286</link>
		<dc:creator>Tim Gaden</dc:creator>
		<pubDate>Sat, 24 Mar 2007 11:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-112286</guid>
		<description>Tom -- it&#039;s a more complicated scenario than you describe, I think.

The Delsp option used by Mail is in the RFC, so Apple is following the standard. The problem is that no one else is. 

This raises an interesting philosophical question about the nature of RFCs (should they codify what everyone does or what everyone &lt;i&gt;should&lt;/i&gt; do?) but doesn&#039;t help Mail users out of their predicament.</description>
		<content:encoded><![CDATA[<p>Tom &#8212; it&#8217;s a more complicated scenario than you describe, I think.</p>
<p>The Delsp option used by Mail is in the RFC, so Apple is following the standard. The problem is that no one else is. </p>
<p>This raises an interesting philosophical question about the nature of RFCs (should they codify what everyone does or what everyone <i>should</i> do?) but doesn&#8217;t help Mail users out of their predicament.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-112236</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Sat, 24 Mar 2007 10:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-112236</guid>
		<description>I&#039;m amazed at the constant bashing of Windows users regarding this issue when it&#039;s clearly mail.app F*ing up here. 
It doesn&#039;t matter that it follows an RFC and everybody else doesn&#039;t - that&#039;s just an arrogant attitude.</description>
		<content:encoded><![CDATA[<p>I&#8217;m amazed at the constant bashing of Windows users regarding this issue when it&#8217;s clearly mail.app F*ing up here.<br />
It doesn&#8217;t matter that it follows an RFC and everybody else doesn&#8217;t &#8211; that&#8217;s just an arrogant attitude.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Peter Reed</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-112224</link>
		<dc:creator>Mike Peter Reed</dc:creator>
		<pubDate>Sat, 24 Mar 2007 09:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-112224</guid>
		<description>I give up.</description>
		<content:encoded><![CDATA[<p>I give up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Peter Reed</title>
		<link>http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/comment-page-1/#comment-112223</link>
		<dc:creator>Mike Peter Reed</dc:creator>
		<pubDate>Sat, 24 Mar 2007 09:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2007/03/24/complicated-solution-to-mailapps-broken-hyperlinks/#comment-112223</guid>
		<description>Except that &#039;&#039; dpn&#039;t show up in comments :-/</description>
		<content:encoded><![CDATA[<p>Except that &#8221; dpn&#8217;t show up in comments :-/</p>
]]></content:encoded>
	</item>
</channel>
</rss>

