>I tried Chris' suggestion about the brackets < & >, and it didn't solve >the fundamental problem, but it did improve the situation slightly. The >long URL was still truncated by a carriage return, which didn't >necessarily work as a link, depending on the other circumstances. For >example, in Emailer, the URL with the brackets was still truncated upon >sending, but even with the unwanted carriage return the URL in the >Emailer inbox still command-clicked open into the browser. However, it >did not command-click tried from a webmail site inbox.
Two other things come to mind. 1: at least in emailer, if you hilite the URL before command clicking, then it can span multiple lines and even have blank lines in it, and Emailer will still properly parse the URL. I have found that to be useful for malformed URLs in the past 2: from a webmail point of view, the URL may do nothing at all if it is does not also include the protocol marker (ie: http://). And, from a webmail point of view, you may be able to fool it into accepting a malformed URL by wrapping it in html code. ie: <a href="http://www.mythtech.net";>www.mythtech.net</a> Even if that gets broken up across multiple lines, a webmail client may still be able to salvage it. White space is meaningless in HTML, so by wrapping it in actual HTML code, you may fool it into ignoring the line breaks. Or you may just wear out your fingers typing extra stuff that doesn't help anyway. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
