<br><div class="gmail_quote">2010/11/5 Arjen de Korte<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">Citeren Arnaud Quette:<br>
<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
we could consider a slightly more complex approach where older asciidoc<br>
detection would only enable the single page html, and pdf version (if<br>
dblatex is also present).<br>
</blockquote>
<br></div>
I'll see what I can do. I already noticed that at least some of the documentation will build with the (old) tools I have, so it might be interesting to do that.</blockquote><div><br>which version are you running?<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
more recent version (once more, the not yet<br>
released 8.6.3) are only needed to build a proper chunked HTML... but I'm<br>
still unsure if it's worth.<br>
</blockquote>
<br></div>
Why not? The clean version strings are available and with the AX_COMPARE_VERSION macro checking the version is easy enough.</blockquote><div><br>the above macro being in place, 1/2 the work is already being done.<br>so let's give it a try if you have 5 mn to do this.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
A transitional solution, to avoid the missing build deps, would be to also<br>
distribute asciidoc outputs, part of the nut tarball, or probably more as<br>
standalone archives.<br>
</blockquote>
<br></div>
How big would they be?</blockquote><div><br>probably enough to justify a separate nut-docs package, that would include the 3 output types...<br><br>here are some approximations on the current version<br>remember that these are not yet polished! and part of this, we have graphical illustrations that could have a major impact on the size.<br>
<br>- PDF :<br>469K docs/developer-guide.pdf<br>184K docs/FAQ.pdf<br>139K docs/packager-guide.pdf<br>728K docs/user-manual.pdf<br><br></div></div>- HTML chunked :<br>
752K docs/user-manual.chunked<br>372K docs/developer-guide.chunked<br>48K docs/packager-guide.chunked<br><br>- HTML single :<br>216K docs/developer-guide.html<br>56K docs/FAQ.html<br>314K docs/user-manual.html<br>
<br>cheers,<br>Arno<br><br>