We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With pandoc 2.9.1.1 (and previous versions) under Debian/unstable, when converting from docbook, the releaseinfo information is missing in the output.
Example manual.xml docbook file:
manual.xml
<?xml version="1.0"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <book> <bookinfo> <title>Title</title> <author> <firstname>Firstname</firstname><surname>Lastname</surname> </author> <releaseinfo>1.17</releaseinfo> </bookinfo> <para>Text.</para> </book>
But with
pandoc -s -f docbook manual.xml -t html pandoc -s -f docbook manual.xml -t texinfo
there is no mention of 1.17 in the output.
The text was updated successfully, but these errors were encountered:
3b563cf
OK, I've added parsing of releaseinfo as metadata, which you can confirm using
pandoc -s -f docbook -t native
However, it won't appear in html or texinfo output unless you use a custom template that includes the releaseinfo variable somewhere.
releaseinfo
Sorry, something went wrong.
DocBook reader: parse releaseinfo as metadata.
08f68fa
Closes #6542. Note that you'll need to put releaseinfo somewhere in your template if you want this to be part of the converted output.
No branches or pull requests
With pandoc 2.9.1.1 (and previous versions) under Debian/unstable, when converting from docbook, the releaseinfo information is missing in the output.
Example
manual.xml
docbook file:But with
there is no mention of 1.17 in the output.
The text was updated successfully, but these errors were encountered: