From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: [bug?] Link to be exported only in HTML
Date: Wed, 04 Feb 2015 08:12:07 -0800 [thread overview]
Message-ID: <87r3u5k65k.fsf@berkeley.edu> (raw)
In-Reply-To: 86wq3xso6m.fsf@example.com
Hi Sebastien,
Sebastien Vauban <sva-news@mygooglest.com>
writes:
> #+TITLE: ECM Links for HTML only
>
> * Test
>
> If I want to include a link (GPL logo, here) to the HTML export, I should put it
> in a block, right?
>
> #+begin_html
> [[http://opensource.org/licenses/GPL-3.0][http://img.shields.io/:license-gpl-blue.svg]]
> #+end_html
>
> Well, that does not work: the link is not rendered as a link; it's copied
> "verbatim".
>
> OTOH, the link on its own is correctly exported to HTML:
>
> [[http://opensource.org/licenses/GPL-3.0][http://img.shields.io/:license-gpl-blue.svg]]
>
> ... but it fails to be exported to LaTeX (causing a "TeX capacity exceeded"
> error), reason why I must not have the link when exporting to LaTeX.
>
> Is this a bug? Is there an alternative?
As far as I understand, this is not a bug: #+begin_html ... #+end_html
is for writing literal HTML that will be included in HTML output.
Thus, if you only care about the link appearing in HTML output, just use
literal HTML:
#+begin_html
<a href="http://opensource.org/licenses/GPL-3.0"><img src="http://img.shields.io/:license-gpl-blue.svg"></a>
#+end_html
(That is hand-translated...you should check whether it is the right HTML for your document.)
Best,
Richard
prev parent reply other threads:[~2015-02-04 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 15:15 [bug?] Link to be exported only in HTML Sebastien Vauban
2015-02-04 15:38 ` Ista Zahn
2015-02-04 22:18 ` Sebastien Vauban
[not found] ` <CA+vqiLGuU_dub1S_bPcNKKighMzRp502a1mcZB5j6UA5LNkA6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-05 11:28 ` Sebastien Vauban
2015-02-04 16:12 ` Richard Lawrence [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=87r3u5k65k.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
/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).