Daniel Barkalow [off-list ref] writes:
It's worth noting that we're a substantial portion of the asciidoc user
base, at least based on asciidoc's "Projects using AsciiDoc" page. We
could probably be influential in the asciidoc development if we tried
(maybe starting with a config file mechanism for controlling what
characters are markup instead of literal, so that we'll be able to make
documents which will work the same with all versions of asciidoc).
Tempting, but...
* The breakage that triggered this thread was not about asciidoc
but about docbook-xsl. AsciiDoc project cannot do much about
it.
* The slowness while formatting our manual pages are 50% from
xmlto toolchain and even if AsciiDoc were were to be sped up
20x, we will still spend 4-5 minutes to format ~140 manual
pages.
On Fri, 3 Aug 2007, Junio C Hamano wrote:
Daniel Barkalow [off-list ref] writes:
quoted
It's worth noting that we're a substantial portion of the asciidoc user
base, at least based on asciidoc's "Projects using AsciiDoc" page. We
could probably be influential in the asciidoc development if we tried
(maybe starting with a config file mechanism for controlling what
characters are markup instead of literal, so that we'll be able to make
documents which will work the same with all versions of asciidoc).
Tempting, but...
* The breakage that triggered this thread was not about asciidoc
but about docbook-xsl. AsciiDoc project cannot do much about
it.
* The slowness while formatting our manual pages are 50% from
xmlto toolchain and even if AsciiDoc were were to be sped up
20x, we will still spend 4-5 minutes to format ~140 manual
pages.
For the latter, asciidoc ought to be able to generate manpages. Not sure
what to do about docbook (for the user manual); it seems generally prone
to compatibility problems. Perhaps we should go through latex instead,
since that's extremely stable these days, or go straight to html.
-Daniel
*This .sig left intentionally blank*