From: Ihor Radchenko <yantar92@posteo.net>
To: Eugen Stan <eugen@ieugen.ro>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode export to html fails for unknown link types - telephone links
Date: Sun, 23 Apr 2023 15:32:48 +0000 [thread overview]
Message-ID: <87y1mi397j.fsf@localhost> (raw)
In-Reply-To: <2b4a2c95-788a-fe15-1172-3a760e056317@ieugen.ro>
Eugen Stan <eugen@ieugen.ro> writes:
> I am building my wedding page with org mode. Yay!.
> I tried to add telephone links so people can click on the link and it
> will do something useful.
>
> I used this markup [[tel:(+40)55-555-555][(+40)55-555-555]] to produce
> something like <a href="tel:(+40)55-555-555">(+40)55-555-555</a> .
>
> However It failed because the tel: is not recognized link.
It is not what is happening.
[[arbitrary text not matching known link type]] links are treated as
fuzzy links searching within current buffer. See 4.2 Internal Links
section of Org manual.
So, Org tries to search for tel:... targets and named elements in
current buffer, fails to do so, and reports that the link is broken to
the user.
> I believe the default behavior of failing to export when encountering an
> unknown link type is not ok.
I hope it is clear now that it is not unknown link type. There is no
such notion in Org as a link with unknown link type.
> Support for tel: links might be added to org-mode by default since it is
> simple to add and quite useful, at least in HTML export .
> See https://css-tricks.com/the-current-state-of-telephone-links/ .
Agree. Patches welcome!
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-04-23 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 10:29 org-mode export to html fails for unknown link types - telephone links Eugen Stan
2023-04-23 15:32 ` Ihor Radchenko [this message]
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=87y1mi397j.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=eugen@ieugen.ro \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).