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

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: 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 15:08:31 +0200	[thread overview]
Message-ID: <87d2dylak0.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87d2dyeaqd.fsf@gmail.com> (Eric Schulte's message of "Tue, 24 Jun 2014 08:46:34 -0400")

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?

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

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,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-06-24 13:08 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 [this message]
2014-06-24 13:30       ` Eric Schulte
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=87d2dylak0.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).