From: Baoqiu Cui <email@example.com>
Subject: Re: DocBook exporter code (version 1.0)
Date: Sun, 08 Mar 2009 21:46:26 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Carsten Dominik <email@example.com> writes:
> Hi Baoqui,
> thanks for the link to the code.
> Forgive me for so far staying quiet on this subject. When you
> first posted the announcement, I had some mixed feelings.
No problem at all. This is totally understandable.
> First of all, I don't really know docbook, and I have never used it.
> One of the really weak features in Org's design is that exporting is not
> implemented in a generic way. All exporters share a preprocessing step
> that turns Org format into something a little more sane and consistent.
> Then each exporter goes its own way. This setup makes maintenance
> sort of a nightmare, because each change to Org syntax needs to be
> implemented in all exporters separately. ...
Yes, it would be nice to have a generic exporting framework in Org.
When I just started working on the DocBook exporter, I tried to follow
org-export-latex.el first but hit some limitation in org-list-to-generic
after a short time. Then I switched to the style of org-export-as-html,
and found its line-based exporting very easy to use.
> ... Maybe you have read my
> swearing when I was trying to fix the LaTeX exporter which I did
> not understand completely at first - it was written by Bastien.
I haven't read about this, but I can imagine what kind of difficulty you
> I had really hoped that the next step in exporting Org would be
> to rewrite the exporter from scratch, in a generic way, that will
> then make supporting different formatters more stable and easy.
> Adding a new exporter does not get us closer to that idea.
Agreed. If Org documents can be parsed into tree representations by the
generic exporter, and each individual exporter only needs to configure
the tags (or formatting methods) for all components in the tree, writing
different exporters would be much easier. Not sure if this can be
easily done in Org.
> And I had feared that your exporter would be a badly hacked
> attempt reinventing lots of wheels, that could never become a really
> complete export.
> I have misjudged severely, the exporter you made looks quite complete,
> you have based it very heavily on the XHTML exporter and in this way
> it seems to be able to handle the entire Org syntax, if I see
> correctly. ...
Yes, DocBook exporter is heavily based on the XHTML exporter. Both
exporters shares a lot of processing, but differ at other areas. Some
internal functions used by these two exporters could be merged in the
> ... So I have now made the changes you require in org-exp.el,
> and I would like to include the exporter, once you are satisfied,
> into our contrib directory or even, depending on copyright assignment,
> into the core.
Thanks a lot for making the changes in org-exp.el! I've removed the
modified version of org-exp.el from my repository on Google Code. I'll
try to do more testing (including testing it on XEmacs) and incorporate
any comments that other people may have before you can put this exporter
into Org release.
> However, I need to make clear that I have no time to maintain another
> exporter, so I would hope that you would be willing to to the necessary
> work to keep it up to date and working.
I won't have any problem with maintaining this exporter.
> Best wishes
> - Carsten
> On Mar 8, 2009, at 6:10 AM, Baoqiu Cui wrote:
>> I just posted the code for DocBook exporter to Google Code. You can
>> the following link to get access to the code and example files:
>> Here is the README:
>> = =
>> # File: org-docbook/README
>> # $Id$
>> This is the DocBook exporter for Org-mode, a tool written in Emacs
>> to export text files written in Org-mode to DocBook.
>> This directory contains:
>> This file.
>> The main part of DocBook exporter code.
>> Slightly modified version of file org-exp.el that is part of
>> Org-mode. Currently this file is synced up with Org-mode 6.24.
>> An Org file used for testing. It includes all the features that
>> current version of DocBook exporter supports.
>> DocBook XML file exported from test.org.
>> PDF file generated from DocBook XML file test.xml.
>> If you have any comments on how to improve this exporter, please send
>> email to cbaoqiu AT yahoo DOT com.
>> = =
>> You are welcome to try this out, and give me any comments you may
>> Bug reports and ideas on how to improve this will be highly
next prev parent reply other threads:[~2009-03-09 4:46 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
2009-03-08 13:46 ` Carsten Dominik
2009-03-09 4:46 ` Baoqiu Cui [this message]
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
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 \
* 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).