On Tue, Mar 26, 2019 at 09:06:03PM -0400, Todd Zullinger wrote: > 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. ;) I noticed the "Release beer" lines in the Asciidoctor relnotes... :) > 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. In our documentation CI build jobs we check that nothing is written to Asciidoc/Asciidoctor's standard error [1]. These "Note:" lines go to stderr, and will trigger that check and cause the build to fail. So wither we should find a way to silence these notes, or filter them out in the CI builds. [1] 505ad91304 (travis-ci: check AsciiDoc/AsciiDoctor stderr output, 2017-04-26), though it never actually worked as intended, but that is about to get fixed: https://public-inbox.org/git/20190324215534.9495-7-szeder.dev@xxxxxxxxx/
