Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.misc > #1093

Re: Nine Lessons Other Desktops Can Learn from KDE

Show all headers | View raw

Lewis <g.kreme@gmail.com.dontsendmecopies>:

> It would also be nice if your posting thingy didn't force-wrap URLs.

You know, there's an actual standard for that (RFC 1738):

   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>.

But then, RFC 2396 gives up on the idea:

   Within certain document media types, the base URI of the document can
   be embedded within the content itself such that it can be readily
   obtained by a parser. This can be useful for descriptive documents,
   such as tables of content, which may be transmitted to others through
   protocols other than their usual retrieval context (e.g., E-Mail or
   USENET news).

   It is beyond the scope of this document to specify how, for each
   media type, the base URI can be embedded.


Marko

Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-27 15:33 +0000
  Re: Nine Lessons Other Desktops Can Learn from KDE "jonh" <jon@nada-sub.co.uk> - 2014-02-27 11:41 -0600
    Re: Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-28 15:33 +0000
  Re: Nine Lessons Other Desktops Can Learn from KDE Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-28 11:24 +0000
    Re: Nine Lessons Other Desktops Can Learn from KDE Marko Rauhamaa <marko@pacujo.net> - 2014-02-28 13:50 +0200
      Re: Nine Lessons Other Desktops Can Learn from KDE Bjoern Hoehrmann <bjoern@hoehrmann.de> - 2014-02-28 14:04 +0100
    Re: Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-28 13:47 +0000
      Re: Nine Lessons Other Desktops Can Learn from KDE Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-03-01 00:46 +0000
    Re: Nine Lessons Other Desktops Can Learn from KDE RS Wood <rsw@therandymon.com> - 2014-02-28 14:01 +0000
      Re: Nine Lessons Other Desktops Can Learn from KDE Mike Easter <MikeE@ster.invalid> - 2014-02-28 08:03 -0800

csiph-web