On Jan 31, 2010, at 1:16 PM, Harold Fuchs wrote:
In the [email protected] list
> James Knott wrote:
>>> The best way to sent a URL is to enclose it in < > brackets, which will
>>> prevent it from being broken in an email.
>>
>> <snip>
>
> The above is simply wrong. The < > brackets make no difference whatsoever.
It does on some programs.
> The main culprits are Mac users. If a Mac user *sends* a long URL, chances
> are it'll arrive broken in most non-Mac mail readers. I don't know why. I do
> know it's possible for the Mac sender to fix it but I don't know how. I do
> know that using < > brackets is *not* part of the solution.
Nonsense. It's the program that matters, not the operating system it runs under.
Historically, what you were /supposed/ to do was enclose thus: <URL:...>
But a large number of programs did not support it, and it was eventually
withdrawn as a standard (or perhaps it was only a recommendation). Some
programs, however, still support it. And some support <...>, even though that
was never a standard.
--
John W Kennedy
"Though a Rothschild you may be
In your own capacity,
As a Company you've come to utter sorrow--
But the Liquidators say,
'Never mind--you needn't pay,'
So you start another company to-morrow!"
-- Sir William S. Gilbert. "Utopia Limited"
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
