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

From: Eric Schulte <schulte.eric@gmail.com>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: how to handle backend-specific types as fuzzy link targets during export
Date: Tue, 24 Jun 2014 09:30:42 -0400	[thread overview]
Message-ID: <87mwd2cu4d.fsf@gmail.com> (raw)
In-Reply-To: <87d2dylak0.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 24 Jun 2014 15:08:31 +0200")

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

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Sure.  I have added a function to org-export-filter-parse-tree-functions
>> which replaces a custom keyword with either a latex-fragment or an HTML
>> link wrapped in a paragraph depending on the export backend.  The latex
>> fragment basically has the following content,
>>
>>     "\\begin{figure}
>>       \\centering
>>       \\input{%s}
>>       \\caption[%s]{\\label{%s}%s}
>>     \\end{figure}\n\n"
>>
>> and I assign it a :name property to match the label in the above.  I
>> then have links elsewhere in the file which reference this label.
>
> I still do not get it. Could you show your (possibly simplified) filter
> function?
>

Attached


[-- Attachment #2: tikz-figure-keywords.el --]
[-- Type: application/emacs-lisp, Size: 2211 bytes --]

[-- Attachment #3: Type: text/plain, Size: 919 bytes --]


>
> Also, what code do you want ox-latex to generate?
>

So something like the following

    #+name: technique-overview
    #+Caption[Overview of Technique]: Text.
    #+TIKZ_FIGURE: technique-overview

    Lorem ipsum dolor sit amet Figure [[technique-overview]] posuere.

results in something like the following for latex export

    \begin{figure}
      \centering
      \input{technique-overview}
      \caption[Overview of Technique]{\label{technique-overview}Text.}
    \end{figure}

     Lorem ipsum dolor sit amet Figure \ref{technique-overview} posuere.

Thanks,
Eric

>
> Note that #+NAME is internal Org syntax. It cannot possibly be
> compatible with random raw LaTeX code. IOW, even if you can write raw
> LaTeX in an Org buffer, it doesn't mean that Org will understand the
> LaTeX code you wrote.
>
>
> Regards,

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)

next prev parent reply	other threads:[~2014-06-24 13:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 10:59 how to handle backend-specific types as fuzzy link targets during export Eric Schulte
2014-06-24 11:56 ` Nicolas Goaziou
2014-06-24 12:46   ` Eric Schulte
2014-06-24 13:08     ` Nicolas Goaziou
2014-06-24 13:30       ` Eric Schulte [this message]
2014-06-24 15:28         ` Nicolas Goaziou
2014-06-30 16:37           ` Eric Schulte
2014-06-30 20:29             ` 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=87mwd2cu4d.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --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

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