Jeff King <peff@xxxxxxxx> writes: > So in my mind, the endgame is that we eventually drop asciidoc in favor > of asciidoctor. The repo at: > > https://github.com/asciidoc/asciidoc > > says: > > NOTE: This implementation is written in Python 2, which EOLs in Jan > 2020. AsciiDoc development is being continued under @asciidoctor. ;-) > I'm not sure when is the right time to switch. If we can get the output > at parity, I don't think asciidoctor is too onerous to install (and we > don't have to worry about ancient platforms, as they can use > pre-formatted manpages). One minor thing that bothers me abit is the continuity of the pre-formatted pages when I switch to asciidoctor to update them. I do not mind having to see a huge diff in the "git log -p" output run in pre-formatted manpages and htmldocs repositories at the boundary due to e.g. the differences how lines are broken or folded between the formatters, but by the time we have to transition, the efforts by you, Martin and friends to allow us compare the formatted docs would have made the real differences to empty (or at least negligible). Knock knock...
