aboutsummaryrefslogtreecommitdiff
path: root/test/docbook-xref.native
AgeCommit message (Collapse)Author
2024-09-14Parse id, class, and tabstyle on tables in DocBook ReaderErik Rask
Add parsing of id (xml:id), class, and tabstyle XML attributes for table and informaltable in the DocBook reader. The tabstyle value is put in the 'custom-style' attribute. fixes #10181
2023-03-22DocBook reader: handle "book" for xref referencesAndres Freund
This also adds a test xref to book and part. See also 4ea0508e6 / #8712.
2023-03-05DocBook reader: parse `figure` as a Figure element in the AST.John MacFarlane
Closes #8668.
2023-02-15fixed <xref> references to tables in DocBook filesPavol Otto
Closes #8626.
2022-05-11Improved reading <xref> elements in DocBook files (#8065)Frerich Raabe
<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.
2021-11-08Add `<titleabbr>` support to DocBook readerRowan Rodrik van der Molen
2021-09-28Switch from pretty-simple to pretty-show for native output.John MacFarlane
Update tests. Reason: it turns out that the native output generated by pretty-simple isn't always readable by the native reader. According to https://github.com/cdepillabout/pretty-simple/issues/99 it is not a design goal of the library that the rendered values be readable using 'read'. This makes it unsuitable for our purposes. pretty-show is a bit slower and it uses 4-space indents (non-configurable), but it doesn't have this serious drawback.
2021-09-21Use pretty-simple to format native output.John MacFarlane
Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.)
2018-07-30DocBook reader: metadata handling improvements.John MacFarlane
Now we properly parse title and subtitle elements that are direct children of book and article (as well as children of bookinfo, articleinfo, or info). We also now use the "subtitle" metadata field for subtitles, rather than tacking the subtitle on to the title.
2017-02-04Moved tests/ -> test/.John MacFarlane