Improved reading <xref> elements in DocBook files #8065
Conversation
<xref> elements can also be used to link to <figure> elements. Alas, the DocBook reader was not aware of this and thus generated a link text which just said 'figure_title'. https://tdg.docbook.org/tdg/4.5/figure.html explains that <figure> elements can contain <title> elements, so let's try to use that if it is available.
|
Thanks very much! |
|
Whoa. Thanks! Funny. Am I since 7 years the only one trying to survive in corporate environment writing in asciidoctor(-pdf), where .docx is needed as standard documents and want to get there via docbook and pandoc? |
I don't know, maybe you are! :-) However, maybe you're also just the first person to exercise the |
|
If you would be so kind and build a "nightly" windows version for me of this latest state, so I would be able to test it further. ;) |
|
Nightlies are built automatically. See the actions tab. |
<xref>elements can also be used to link to<figure>elements. Alas, the DocBook reader was not aware of this and thus generated a link text which just said 'figure_title'.https://tdg.docbook.org/tdg/4.5/figure.html explains that
<figure>elements can contain<title>elements, so let's try to use that if it is available.Technically, this logic could be a lot more sophisticated. The docbook-xsl project's XSLT stylesheet for handling
<xref>elements is a whopping 1300+ lines of code, and a lot of that is dedicated to a comprehensive heuristic which tries to come up with a sensible link text depending on the target element being referenced. However, it took seven years for someone to point out that Pandoc's handling of<xref>elements is incomplete, so maybe we don't need to go all the way just yet.Closes #8064 .