emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [export] latex: texorpdfstring in heading
Date: Tue, 25 Nov 2014 15:55:02 +0100	[thread overview]
Message-ID: <87egsr72k9.fsf@gmx.us> (raw)
In-Reply-To: olu8uiz4dok.fsf@med.uni-goettingen.de

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Hi,
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> Hello,
>>
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>> So, here is my question: How do I use \texorpdfstring correctly in an
>>> org heading?
>>>
>>>
>>> And here is a minimal example:
>>>
>>> #+latex_header: \usepackage{hyperref}
>>>
>>> * This contains \texorpdfstring{$\prod_{k=1}^N$}{product 1toN} math
>>> For some reason.
>>
>>   * This contains @@latex:\texorpdfstring{$\prod_{k=1}^N$}{product
>> 1toN}@@ math
>>
>
> There is now the obvious follow-up question: What do I do if I want to
> export that same document to other backends as well?
>
> I assume I'd have to list each of the others individually as well like:
> @@latex:foo@@ @@html:bar@@ @@ascii:bar@@ @@odt:bar@@ ?

You could use a macro if it's only for one document, see
(info "(org) Macro replacement").

Otherwise you could use a custom link and cond through your backends
backends, see `org-add-link-type' or
(info "(org) Adding hyperlink types").

Hope it helps,
Rasmus



-- 
And I faced endless streams of vendor-approved Ikea furniture. . .

  reply	other threads:[~2014-11-25 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 15:16 [export] latex: texorpdfstring in heading Andreas Leha
2014-11-24 16:22 ` Eric S Fraga
2014-11-25  1:25   ` Andreas Leha
2014-11-25 11:16     ` Eric S Fraga
2014-11-24 16:24 ` Nicolas Goaziou
2014-11-24 21:15   ` Andreas Leha
2014-11-25 13:23   ` Andreas Leha
2014-11-25 14:55     ` Rasmus [this message]
2014-11-25 15:00       ` Nicolas Goaziou
2014-11-25 15:07         ` Andreas Leha

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=87egsr72k9.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).