From: Igor Lumpus <igorlopez.gbg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Converting from Doc-book to Markdown fails for biblioentry->title and bibliomixed->title
Date: Mon, 13 Sep 2021 07:19:49 -0700 (PDT) [thread overview]
Message-ID: <07c131fd-6189-473d-af2f-b74c0d0a47fen@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1398 bytes --]
I am trying to convert doc-book xml that contains bibliography tags like:
<bibliography>
<title>Bibliography</title>
<biblioentry>
<abbrev>A1</abbrev>
<title>Test doc A1</title>
</biblioentry>
<bibliomixed>
<abbrev>A2</abbrev>
<title>Test doc A2</title>
</bibliomixed>
</bibliography>
by running the command (from Powershell on a WIndows 10 PC)
> pandoc.exe -f docbook -t markdown -s 'simple.xml' -o simple.md
Note, the above cutout tested both using biblioentry and bibliomixed tags
with no impact.
The output file lacks the title element where it looks like:
# Bibliography
A1
A2
whereas my expectations would have been something like this in simplest
form:
# Bibliography
A1:Test doc A1
A2:Test doc A2
and an even better markdown output would have created a table like:
# Bibliography
|abbrev | title |
| --- | --- |
|A1|Test doc A1|
|A2|Test doc A2|
Any thoughts?
--
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/07c131fd-6189-473d-af2f-b74c0d0a47fen%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2884 bytes --]
reply other threads:[~2021-09-13 14:19 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07c131fd-6189-473d-af2f-b74c0d0a47fen@googlegroups.com \
--to=igorlopez.gbg-re5jqeeqqe8avxtiumwx3w@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).