Hi, I wrote: > Jeff King wrote: >> That seems like a bug in asciidoctor, which ought to be quoting the "<". >> We certainly can't quote it ourselves (we don't even know that our >> backend output is going to a format that needs angle brackets quoted). > > Yep, it seems so. I filed this upstream: > > https://github.com/asciidoctor/asciidoctor/issues/3205 > > I updated to asciidoctor-2.0.1 this morning to test, in case > it was one of the issues fixed since the 2.0.0 release. > Alas, we're the first to hit it and report it. Dan Allen fixed this upstream and released 2.0.2 today. It's very good to know that asciidoctor upstream is incredibly responsive. If anyone runs into Dan at a conference, please buy him a beer. ;) 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. -- Todd
