From: Rustom Mody <firstname.lastname@example.org>
To: emacs-orgmode <email@example.com>
Subject: Re: docbook export-special
Date: Thu, 28 May 2009 13:17:22 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Rustom Mody <rustompmody <at> gmail.com> writes:
> Baoqiu wrote:
>> What do you mean by export-special?
> Well the latest org comes with a contributed org-special-blocks.el
> [sorry I misnamed it]
>> Do you mean exporting blocks that look like the following lines?
> Yes I guess that would be what I want.
> Thanks for the confirmation, Rustom. Carsten and I had several email
> exchanges on this topic last month, and we decided to not support such
> special blocks in DocBook exporter (see the following email).
> Can you use #+BEGIN_DOCBOOK ... #+END_DOCBOOK instead to achieve what
> you want?
Well something would be better than nothing :-)
My own view: latex and html are very different from docbook.
1. latex and html are specific presentation formats as against docbook
which is a general content format
2. Conversely no one wants to use docbook for itself but rather as a
stepping stone to something else -- typically pdf/html but in
principle any arbitrary 'end'-format. This means that
docbook-exporter allowing for potential docbook errors is a smaller
problem than making impossible something which
a. can be/is already available in org
b. is supported in the 'end'-format
c. but is unavailable in the interim (docbook)
One such thing which may not be meaningful in latex and html but is a
lack in docbook is property exports.
Maybe if you or Carsten feel this should not go into org then
org-special-blocks is the place for it?
next prev parent reply other threads:[~2009-05-28 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 14:01 docbook export-special Rustom Mody
2009-05-26 23:49 ` Baoqiu Cui
2009-05-27 6:29 ` Rustom Mody
2009-05-27 18:46 ` Baoqiu Cui
2009-05-28 7:47 ` Rustom Mody [this message]
2009-05-28 9:00 ` Carsten Dominik
2009-05-28 12:16 ` Rustom Mody
2009-05-28 16:49 ` Baoqiu Cui
2009-06-03 12:28 ` Rustom Mody
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).