From: Diane Reeve <dreeve-2mpuytILhGg@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: No PDF output from DocBook <info> elements...
Date: Fri, 10 Dec 2021 07:08:03 -0800 (PST) [thread overview]
Message-ID: <f3dc078c-e291-4a4e-9048-ef62aa4847fdn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
New to pandoc, so apologies if this is a dumb question.
I have a DocBook 5.0 book with an <info> element containing various
meta-data and the same document in DocBook 4.5 with the equivalent
<bookinfo> element.
When I process with pandoc to PDF the <info> meta data (publication date,
rights info, etc.) is not rendered: I get a title page, then immediately a
toc and the subsequent chapters. Same story with the 4.5 version's
<bookinfo> element.
The pandoc reference on supported DocBook tags says that <info> is
supported, so I imagine I might be missing a processing option somewhere.
Can anyone point me in the right direction?
DJR
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f3dc078c-e291-4a4e-9048-ef62aa4847fdn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1462 bytes --]
next reply other threads:[~2021-12-10 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 15:08 Diane Reeve [this message]
[not found] ` <f3dc078c-e291-4a4e-9048-ef62aa4847fdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-10 16:59 ` John MacFarlane
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3dc078c-e291-4a4e-9048-ef62aa4847fdn@googlegroups.com \
--to=dreeve-2mpuytilhgg@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).