From: Peter Davis <pfd@pfdstudio.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: emacs-orgmode@gnu.org
Subject: Re: Making DocBook xml books from org mode?
Date: Fri, 30 Sep 2016 11:44:09 -0400 [thread overview]
Message-ID: <1475250249.663446.742041297.1ACDFDFD@webmail.messagingengine.com> (raw)
In-Reply-To: <1475187422.3176053.741333169.0906F627@webmail.messagingengine.com>
To follow up ...
On Thu, Sep 29, 2016, at 06:17 PM, Peter Davis wrote:
> On Thu, Sep 29, 2016, at 03:23 PM, Joost Kremers wrote:
> >
> > Pandoc can convert to Docbook, so that might be an option. Note that
> > Pandoc also converts *from* Org, (although it cannot handle all of Org's
> > capabilities), so depending on your needs, that might be a way to go
> > directly from Org to Docbook.
> >
>
> Thank you. I did succeed in exporting from org to texi, and then
> makeinfo'ing that into a DocBook xml, though a bit of hand editing was
> necessary.
>
I did manage to get this working. I found I had to export to Pandoc
instead of running pandoc from a command line with the org file as
input. Otherwise, the embedded dot code I used would not link to an
image, but simply contain the dot code as source.
Unfortunately, in trying to export to a file, I'm getting
Unable to resolve link "www.gimp.org/downloads"
I don't know where this is coming from, or how to fix it.
Finally, the 'Export with Pandoc' menu item only gives me two choices:
[P] Markdown to buffer
[p] To file
I assume it's just generating Markdown, which would then have to be
converted to docbook or whatever in a separate step. Any way to export
to docbook directly, using Pandoc implicitly?
Thanks!
-pd
--
Peter Davis
www.techcurmudgeon.com
next prev parent reply other threads:[~2016-09-30 15:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 18:04 Making DocBook xml books from org mode? Peter Davis
2016-09-29 19:23 ` Joost Kremers
2016-09-29 22:17 ` Peter Davis
2016-09-30 15:44 ` Peter Davis [this message]
2016-10-02 21:23 ` Peter Davis
2016-10-02 21:35 ` Joost Kremers
2016-10-02 21:46 ` Peter Davis
2016-10-02 22:12 ` Joost Kremers
2016-10-03 0:32 ` Peter Davis
2016-10-03 2:09 ` Norman Walsh
2016-10-03 12:46 ` Peter Davis
2016-10-03 3:38 ` Marcin Borkowski
2016-10-03 12:49 ` Peter Davis
2016-09-30 9:16 ` [DOCS] " Christian Moe
2016-09-30 14:51 ` Peter Davis
2016-09-30 15:33 ` Thomas S. Dye
2016-09-30 15:46 ` Peter Davis
2016-09-30 19:37 ` Nick Dokos
2016-09-30 19:46 ` Peter Davis
2016-09-30 20:18 ` Colin Baxter
2016-09-30 20:50 ` Nick Dokos
2016-10-01 8:01 ` Colin Baxter
2016-10-05 13:32 ` Peter Davis
2016-09-30 9:37 ` Marcin Borkowski
2016-09-30 14:55 ` Peter Davis
2016-09-30 17:05 ` Nick Dokos
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=1475250249.663446.742041297.1ACDFDFD@webmail.messagingengine.com \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).