From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Still trying to get DocBook output
Date: Mon, 07 Nov 2016 16:21:58 -0500 [thread overview]
Message-ID: <1478553718.3411834.780382289.6049CAE6@webmail.messagingengine.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
Since DocBook XML is not supported by the new org-mode export
architecture, I tried following the recommendation here:
http://orgmode.org/worg/exporters/ox-overview.html
exporting to texi and then using makeinfo to convert to DocBook XML.
This worked reasonably smoothly, though it still required some hand
editing. In particular, there are a number of constructs that seem to be
completely different in org->makeinfo generated XML vs. the DocBook XML
my team is using. I'm not sure this is exhaustive, but here's what I've
found so far:
Effect MakeInfo XML output Desired DocBook XML id strings
Mixed_Case_Section_Title XXXX_lower_case_section_title chapter, sect
labels label="n.n" *n/a* Code example <screen>...</screen>
<programlisting>...</programlisting> Graphic <informalfigure>
<mediaobject> <imageobject> <imagedata fileref="..."
format="..."></imagedata> </imageobject> </mediaobject>
</informalfigure><para><graphic fileref="..." format="..."/><para>
Definition list <variablelist> <varlistentry> <term>...</term>
<listitem> <para>...</para> </listitem> </varlistentry> ...
</variablelist><glosslist> <glossentry> <glossterm>...</glossterm>
<glossdef><para>...</para></glossdef> </glossentry> ... </glosslist>
I hope this HTML table comes through.
I'm assuming I could create a fairly simple XSLT script to convert the
makeinfo output to the desired XML, but I'm wondering if there's a way
to pass a stylefile, DTD or schema to makeinfo to do this automatically.
Anyone know?
I looked at the help for makeinfo, but didn't see anything I recognized
as a way to do this.
Thanks,
-pd
--
Peter Davis
www.techcurmudgeon.com
[-- Attachment #2: Type: text/html, Size: 4361 bytes --]
reply other threads:[~2016-11-07 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=1478553718.3411834.780382289.6049CAE6@webmail.messagingengine.com \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).