emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Christian Egli <christian.egli@sbszh.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to write an exporter
Date: Wed, 25 Jun 2008 10:47:09 +0200	[thread overview]
Message-ID: <D8CECD6C-9958-4ED7-94AF-49BD2206A65F@uva.nl> (raw)
In-Reply-To: <j24p7jgjjq.fsf@sbszh.ch>


On Jun 24, 2008, at 1:27 PM, Christian Egli wrote:

> Hi
>
> I've been wanting to have an exporter for latex beamer and for
> mediawiki. I thought that might be a nice summer project. How do I
> write it? Do I use
>
> - the new mapping API
> - or the "new" exporter engine from Bastien which is buried away
>   somewhere on a branch in git?
>
> I guess the mapping API is included in org-mode proper but only gives
> me access to the headlines AFAIK. What is the status of the exporter
> engine from Bastien? Is it ever going to be resurrected?

Bastien has been quite busy lately, and I am not sure how this will
develop in the future.

The "new export engine" as far as I can see, is so far mostly a parser
that converts an Org file into a structured hierarchy of property lists
that give access to the entire content as well as all the meta data
like tags, todo state, deadline date etc etc.

I have pulled out org-export.el from the branch and placed a copy into
the EXPERIMENTAL subdirectory of the master branch.

Bastien, I fixed a bug which had to do with narrowing in a recursive  
procedure - the old restriction needs to be remembered.  Also, I  
implemented a function that will remove the meta data (most of it  
anyway) from the content string, so maybe this is a useful thing?  It  
is a separate function, so easily removed again.

Looking at org-export.el,  Bastien also planed to have filter  
functions, and then backend that will write the structure back to a  
file - I don't know how much of this works.

Christian, you could simply experiment with the return value of org- 
export-parse.

HTH

- Carsten



>
>
> Thanks
> Christian
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2008-06-25  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 11:27 How to write an exporter Christian Egli
2008-06-25  8:47 ` Carsten Dominik [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=D8CECD6C-9958-4ED7-94AF-49BD2206A65F@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=christian.egli@sbszh.ch \
    --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).