emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alex Ott <alexott@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: DocBook exporter code (version 1.0)
Date: Sun, 08 Mar 2009 10:43:37 +0100	[thread overview]
Message-ID: <m2ab7w8i46.fsf@flash.lan> (raw)
In-Reply-To: <52A4D4D6-E4BB-4ACF-9438-EB69E71ABEA8@uva.nl> (Carsten Dominik's message of "Sun, 8 Mar 2009 08:22:08 +0100")


>>>>> "CD" == Carsten Dominik writes:
 CD> One of the really weak features in Org's design is that exporting is
 CD> not implemented in a generic way.  All exporters share a preprocessing
 CD> step that turns Org format into something a little more sane and
 CD> consistent.  Then each exporter goes its own way.  This setup makes
 CD> maintenance sort of a nightmare, because each change to Org syntax
 CD> needs to be implemented in all exporters separately.  Maybe you have
 CD> read my swearing when I was trying to fix the LaTeX exporter which I
 CD> did not understand completely at first - it was written by Bastien.

 CD> I had really hoped that the next step in exporting Org would be to
 CD> rewrite the exporter from scratch, in a generic way, that will then
 CD> make supporting different formatters more stable and easy.  Adding a
 CD> new exporter does not get us closer to that idea.

I think, that instead of parsing text directly, we need to write generic
exporter, that will export all data as a tree, consisting from header +
list of the entries, and inside these entries provide all needed
information about text (markup, url information, etc.).  And for new export
format, author will define only small piece of code -- mostly header
generation, and replacement tables for formatting tags, urls decorations,

What do you think about this? I can try to define basic API and we'll see
what we can do

 CD> And I had feared that your exporter would be a badly hacked attempt
 CD> reinventing lots of wheels, that could never become a really complete
 CD> export.

With best wishes, Alex Ott, MBA
http://alexott.blogspot.com/        http://xtalk.msk.su/~ott/

  reply	other threads:[~2009-03-08  9:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-08  5:10 DocBook exporter code (version 1.0) Baoqiu Cui
2009-03-08  7:22 ` Carsten Dominik
2009-03-08  9:43   ` Alex Ott [this message]
2009-03-08 13:46     ` Carsten Dominik
2009-03-09  4:46   ` Baoqiu Cui
2009-03-09  6:25     ` Carsten Dominik
2009-03-09 17:21       ` Baoqiu Cui
2009-03-12 16:02 ` Dale Smith
2009-03-13  0:26   ` Baoqiu Cui
2009-03-13  2:05     ` Baoqiu Cui
2009-03-13  3:12       ` Baoqiu Cui
2009-03-13  6:37       ` Carsten Dominik
2009-03-13 13:42         ` Dale Smith

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:

  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=m2ab7w8i46.fsf@flash.lan \
    --to=alexott@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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