mehrzeiligen Link in plain text mail

[Alexander (HH)]

Moin Moin!

Gibt es die RFC für <URL: > irgendwo? Habe nichts ergooglen können..

Das Format ist innerhalb der RFCs selbst relativ beliebt, erstmals taucht es in RFC1738 auf, dann gleich 30 mal. Das ist nicht weiter verwunderlich, denn RFC1738 beschreibt genau die URLs. Und *TADAA!*, im Anhang auf Seite 21  ist dann auch lang und breit diskutiert, wie man URLs in verschiedenen Kontexten (sprich: Plain Text) verpacken soll:

APPENDIX: Recommendations for URLs in Context

URIs, including URLs, are intended to be transmitted through
   protocols which provide a context for their interpretation.

In some cases, it will be necessary to distinguish URLs from other
   possible data structures in a syntactic structure. In this case, is
   recommended that URLs be preceeded with a prefix consisting of the
   characters "URL:". For example, this prefix may be used to
   distinguish URLs from other kinds of URIs.

In addition, there are many occasions when URLs are included in other
   kinds of text; examples include electronic mail, USENET news
   messages, or printed on paper. In such cases, it is convenient to
   have a separate syntactic wrapper that delimits the URL and separates
   it from the rest of the text, and in particular from punctuation
   marks that might be mistaken for part of the URL. For this purpose,
   is recommended that angle brackets ("<" and ">"), along with the
   prefix "URL:", be used to delimit the boundaries of the URL.  This
   wrapper does not form part of the URL and should not be used in
   contexts in which delimiters are already specified.

In the case where a fragment/anchor identifier is associated with a
   URL (following a "#"), the identifier would be placed within the
   brackets as well.

In some cases, extra whitespace (spaces, linebreaks, tabs, etc.) may
   need to be added to break long URLs across lines.  The whitespace
   should be ignored when extracting the URL.

No whitespace should be introduced after a hyphen ("-") character.
   Because some typesetters and printers may (erroneously) introduce a
   hyphen at the end of line when breaking a line, the interpreter of a
   URL containing a line break immediately after a hyphen should ignore
   all unencoded whitespace around the line break, and should be aware
   that the hyphen may or may not actually be part of the URL.

Examples:

Yes, Jim, I found it under <URL:ftp://info.cern.ch/pub/www/doc;
      type=d> but you can probably pick it up from <URL:ftp://ds.in
      ternic.net/rfc>.  Note the warning in <URL:http://ds.internic.
      net/instructions/overview.html#WARNING>.

Die URL:...-Notation ist also "nur" die Kombination aus zwei Empfehlungen, und eben kein "echter" Standard. Man darf auch eine oder beide Empfehlungen weglassen, somit sollte ein ausreichend clever geschriebenes Programm mit allen vier möglichen Varianten (ohne alles, nur "URL:"-Prefix, nur "<...>", "URL:...") einer URL im Fließtext klarkommen. Freundliche Programme und freundliche Menschen, die es anderen Programmen leicht machen wollen, folgen beiden Empfehlungen, d.h. URL:....

So, dann kann ich mein Neuron ja wieder zusammenflicken ... ;-)

Alexander