On Tue, Mar 26, 2019 at 09:06:03PM -0400, Todd Zullinger wrote: > There's still the matter of 2.0 dropping docbook45. I'll > try to get around to testing 1.5.x releases with docbook5 to > see if they work reasonably well. If not, we can add a > version check and set ASCIIDOC_DOCBOOK appropriately. > > One other issue that crops up with docbook5 is that the > xmlto toolchain now outputs: > > Note: namesp. cut : stripped namespace before processing > > as documented at > > https://docbook.org/docs/howto/howto.html#dbxsl > > It's mostly an annoyance which we either want to strip out, > or pass an alternate docbook5 xsl, I think. But I'm not > very familiar with the guts of the xml/docbook toolchains. I'm quite familiar with this area, because I used DocBook and its stylesheets for my college papers. There are two sets of stylesheets, the namespaced ones (for DocBook 5) and the non-namespaced ones (for DocBook 4). They can be distinguished because the URLs (and typically the paths) use "xsl" (for non-namespaced) or "xsl-ns" (for namespaced). xmlto by default uses the older ones, and assuming you have a reasonably capable XSLT processor, either set of stylesheets can be used, since they simply transform the document into the right type (although with a warning, as you've noticed). Unfortunately, xmlto is hard-coded to use the non-namespaced stylesheets with no option to specify which to use, and it doesn't appear to be actively developed. There's an option to specify the stylesheet (-x), but it can't take a URL, since xmlto "helpfully" fully qualifies the path. That means we'd need to know the location on disk of those stylesheets in order to use them, since we can't rely on catalog resolution. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204