emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: docbook export-special
Date: Thu, 28 May 2009 11:00:21 +0200	[thread overview]
Message-ID: <A9B0F8EC-9392-4416-951A-F6F2F53B18AC@gmail.com> (raw)
In-Reply-To: <f46c52560905280047t6f404ebeq959ce79de8d072f9@mail.gmail.com>

On May 28, 2009, at 9:47 AM, Rustom Mody wrote:

> Hello Baoqiu,
> 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?
>>> #+begin_xyz
>>> ...
>>> #+end_xyz
>> 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?
>> Thanks,
>> Baoqiu
> 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.

This, I think, was the reason why we could not see a good way to do  
this in docbook.

- Carsten

> Maybe if you or Carsten feel this should not go into org then
> org-special-blocks is the place for it?

I think you need to come up with a concrete implementation proposal.

- Carsten

> _______________________________________________
> 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:[~2009-05-28  9:00 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
2009-05-28  9:00     ` Carsten Dominik [this message]
2009-05-28 12:16       ` Rustom Mody
2009-05-28 16:49         ` Baoqiu Cui
2009-06-03 12:28         ` Rustom Mody

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=A9B0F8EC-9392-4416-951A-F6F2F53B18AC@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rustompmody@gmail.com \


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