emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thorsten Jolitz <tjolitz@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New exporter: where are the back-end functions called?
Date: Tue, 12 Jun 2012 14:53:04 +0200	[thread overview]
Message-ID: <878vfselov.fsf@gmail.com> (raw)
In-Reply-To: <87ipexy2er.fsf@googlemail.com> (Thorsten Jolitz's message of "Mon, 11 Jun 2012 23:17:00 +0200")

Hello,

Thorsten Jolitz <tjolitz@googlemail.com> writes:

> when trying to enhance the HTML back-end of the new exporter with
> interactive HTML elements, one possibility (probably the easiest and
> best) is to write variants for the export functions for some Org
> elements that insert different HTML in the output string (HTML form
> fields instead of static HTML).
>
> By far the most interesting Org element for me is the 'headline'
> element, that is transcoded by the following function from
> 'org-e-html.el': 
>
> ,--------------------------------------------------------------
> | (defun org-e-html-headline (headline contents info)
> |   "Transcode an HEADLINE element from Org to HTML.
> | CONTENTS holds the contents of the headline.  INFO is a plist
> | holding contextual information."
> `--------------------------------------------------------------
>
> Now I don't want to mess around in the original exporter code, but
> rather would like to rename this function and all the helper functions
> it calls with the 'iorg'-prefix and then experiment with changing the
> function bodies.

You may have a look at `org-export-define-derived-backend' macro and
"Defining a Back-End" in Org export documentation[1].


Regards,

[1] http://orgmode.org/worg/dev/org-export-reference.html

-- 
Nicolas Goaziou

      reply	other threads:[~2012-06-12 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 21:17 New exporter: where are the back-end functions called? Thorsten Jolitz
2012-06-12 12:53 ` Nicolas Goaziou [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=878vfselov.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tjolitz@googlemail.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
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).