"Thomas Adam" [off-list ref] writes:
Something the ELinks project does is distribute a fixed version
of the asciidoc script to avoid annoying asciidoc errors each
time there's a new asciidoc release.
Actually, we only distribute the AsciiDoc configuration files.
I should perhaps add the actual asciidoc Python script to the
ELinks source tree as well. That seems to be the recommendation
in the AsciiDoc manual.
http://www.methods.co.nz/asciidoc/userguide.html#_shipping_stand_alone_asciidoc_source