On Mon, Mar 23, 2015 at 07:18:45PM +1100, Lex Trotman wrote: > On 23 March 2015 at 18:45, Marco Ciampa <[email protected]> wrote: > > On Mon, Mar 23, 2015 at 10:00:21AM +1100, Lex Trotman wrote: > >> Hi Ken, > >> > >> On [[is,xreflabel]] the manual says " The optional <xreflabel> is only > >> really useful when generating DocBook output.". > >> > >> That is because the docbook toolchains copy the xreflabel to the > >> reference from the anchor. > >> > >> Since the HTMLs are generated directly by Asciidoc there is no > >> toolchain to do that. Asciidoc itself can't because it is a streaming > >> processor that does not load the whole document in one go. > > > > THAT is a big limit! > > Hi Marco, > > Its such a big limit that nobody has submitted a change to remove it to date > :) > > Seriously though it would be a complete re-write like asciidoctor. > > And the docbook xslt toolchain produces html without javascript.
I missed this! I was always asking myself the reason why to have 2 different methods to produce HTML, that is a _good_ reason! Using HTML as an output doc format means that something there is the need to show doc text with a stripped down html viewer, without javascript and such... Thanks for the hint! -- Marco Ciampa I know a joke about UDP, but you might not get it. +------------------------+ | GNU/Linux User #78271 | | FSFE fellow #364 | +------------------------+ -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
