5 ms·
> it's been my experience that many receiving email clients break overly long URLs I always use the "embed in angle brackets" trick for that--although I don't
by follower 16y ago
> it's been my experience that many receiving email clients break overly long URLs
I always use the "embed in angle brackets" trick for that--although I don't know how all mail readers render it:
<http://news.ycombinator.com/>
- Hixie 16y agoThat convention drives me batty. So much time wasted when trying to copy-and-paste those URLs.
- jemfinch 16y agoThat "convention" is one of the only standards-compliant ways to delimit URLs. Fix your copy-and-paste mechanism.
- ralph 16y agoWhat standard says <http://news.ycombinator.com/> http://news.ycombinator.com/>? The appendix of http://www.ietf.org/rfc/rfc1738.txt http://www.ietf.org/rfc/rfc1738.txt says <URL:http://news.ycombinator.com/> http://news.ycombinator.com/>.
- jemfinch 16y agoRead closer. "The characters '<' and '>' are unsafe because they are used as the delimiters around URLs in free text". The RFC itself uses "<URL:...>" because it already uses "<...>" for BNF non-terminals, which are much more common than URLs in the RFC. Enjoy your undeserved upvote :)