From: Baoqiu Cui <email@example.com>
Subject: Re: docbook export-special
Date: Thu, 28 May 2009 09:49:40 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Rustom Mody <email@example.com> writes:
> On Thu, May 28, 2009 at 2:30 PM, Carsten Dominik
> <firstname.lastname@example.org> wrote:
>> On May 28, 2009, at 9:47 AM, Rustom Mody wrote:
>>> Hello Baoqiu,
>>> Rustom Mody <rustompmody <at> gmail.com> writes:
>>>> Baoqiu wrote:
>>>> Can you use #+BEGIN_DOCBOOK ... #+END_DOCBOOK instead to achieve what
>>>> you want?
> Hell! I could swear that I tried this yesterday and the content disappeared!
> Today its appearing in the xml output so thats probably enough.
I am very glad to know that this works for you.
> I worked out the current mappings as i find them:
> 1 BEGIN_QUOTE -> <blockquote>
> 2 BEGIN_EXAMPLE -> <programlisting>
> 3 BEGIN_SRC lang -> <programlisting>
> 4 BEGIN_VERSE -> <literallayout>
> 5 BEGIN_CENTER -> something complicated
Yes, the above mappings are what I use now in the exporter.
BEGIN_CENTER is handled using <informaltable>.
Have you tried something like the following?
#+DOCBOOK: <para><emphasis>One line</emphasis> written in DocBook</para>
<para>You should know what you are doing when quoting DocBook XML code
in your Org file. Invalid DocBook XML file may be generated by
DocBook exporter if you are not careful!</para>
Because we already have #+BEGIN_DOCBOOK ... #+END_DOCBOOK, there is no
point to support many other blocks like #+begin_warning
... #+end_warning (for the above example) etc., which can really pollute
> It would ne nice if something like this is there at least in the
> org-docbook.el sources -- The manual is long enough and need not be
> lengthened with the requirements of fringe users like
> Yours truly :-)
I can add a little more comments in org-docbook.el, but ideally we
should add important things to the manual if they are missing. What
particular information do you want to see in the manual?
next prev parent reply other threads:[~2009-05-28 16:50 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
2009-05-28 12:16 ` Rustom Mody
2009-05-28 16:49 ` Baoqiu Cui [this message]
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).