emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ben McGinnes <ben@adversary.org>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: is ascii link format canonical? can it be made more linkifiable?
Date: Wed, 7 Feb 2018 06:43:33 +1100	[thread overview]
Message-ID: <20180206194333.kavoapxfaf36jkpr@adversary.org> (raw)
In-Reply-To: <CAJcAo8tbLhHb4NRwgvDadVkkcSo4XO99SBTGa83E+wLoZsyEtA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

On Mon, Feb 05, 2018 at 09:26:14PM -0700, Samuel Wales wrote:
> 
>   [[http://whatever.com]]
> 
> i do not know the standard, but i think that some email clients will
> not linkify this because of the brackets.

Correct.

> are we sure that [] are canonical?  not <>?  is it the clients that
> are wrong?

No, it's because the square brackets are valid characters for use in
file names and thus can be part of the URL itself.  There's no way for
a MUA to recognise the difference.

You can see this demonstrated here:

http://www.adversary.org/test/]

And here:

http://www.adversary.org/test/]]

Angle brackets, however, are not valid in URLs and recognisably used
within HTML, XHTML, XML and variants.  Since most MUAs achieve their
WYSIWIG interfaces via some means of implementing HTML (or a
bastardisation of it), the angle brackets are recognised as a means of
specifying a particular type of object.  Some MUAs will leverage the
mailcap file to be more specific with this.  Some, of course, won't
and some wander off on strange bastardised rich text tangents or
custom protocols (insert pointed look at Microsoft Outlook here).

Mostly, though, GUI MUAs went for HTML 4.01 and/or an XHTML variant
after Netscape Communicator hit the Net in the late '90s and everyone
(eventually) followed suit.  Along with retaining some simplistic
carry over from plain text emails similar to basic text mark-up in
org-mode (e.g. *bold*, /italics/, _underline_ and so on).  Most of
which were de facto standards, not official ones.  Basically the geek
equivalent of demonstrating how custom and tradition were more
pervasive than law (RFCs and MUA design).


Regards,
Ben

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

next prev parent reply	other threads:[~2018-02-06 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06  4:26 is ascii link format canonical? can it be made more linkifiable? Samuel Wales
2018-02-06 19:43 ` Ben McGinnes [this message]
2018-02-10 13:18 ` Nicolas Goaziou
2018-02-10 18:58   ` Samuel Wales
2018-02-11  9:16     ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180206194333.kavoapxfaf36jkpr@adversary.org \
    --to=ben@adversary.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).