I didn't try but I guess it would work. The only thing is that one of the reasons I use asciidoc is that I didn't want to take the time to learn and remind more complex syntax.
But yes, it should normally be processed correctly. Someone who knows how to directly write the passthrough block using docbook could try and tell us if it is processed correctly (and give us an example). That would be great. Regards, Joseph On Mon, Jul 29, 2013 at 4:46 PM, Eduardo Santana <[email protected]>wrote: > I understand it, but even if you are writing to HTML or PDF, if you are > using the docbook backend, then the Passthrough will docbook code. And > should work for both, right? > > > Em quarta-feira, 24 de julho de 2013 14h47min49s UTC-3, Joseph Herlant > escreveu: >> >> Hello Eduardo, >> >> The issue with the Passthrough Block is that it is that it only applies >> to one language at a time. >> If you want to publish either in HTML or PDF (using latex), you have to >> modify your Passthrough block for one or the other. Furthermore, you have >> to know how to make a table using latex or hmtl (which is not really hard, >> but you have to rewrite all the syntax). >> The method I proposed is using the same syntax than asciidoc, so anybody >> that knows asciidoc can use without having to care for the publication >> format one will use. Which is more the asciidoc way to do this (from what I >> understood of asciidoc!). >> :) >> >> Regards, >> Joseph >> >> >> Le lundi 22 juillet 2013 16:05:29 UTC+2, Eduardo Santana a écrit : >>> >>> Did you try to use a Passthrough Block? >>> >>> ++++ >>> (docinfo contains) >>> ++++ >>> >>> Em domingo, 7 de julho de 2013 10h16min44s UTC-3, Joseph Herlant >>> escreveu: >>>> >>>> Hello, >>>> >>>> For generating revision history, I use the <filename>-docinfo.xml file. >>>> To generate this more easily, I made a little script >>>> (docinfo_generator.py) I posted at: https://github.com/aerostitch/** >>>> asciidoc-tools <https://github.com/aerostitch/asciidoc-tools> >>>> I know this is quite an old post, but I wasn't really able to find a >>>> tool that would help me not to have many files to maintain. I wanted to be >>>> able to have only one text file to maintain: the asciidoc text file. >>>> >>>> The principle of the script is simple: >>>> You add the revision history informations (or legal notice, or >>>> copyright) in a comment block of your asciidoc file. >>>> The script will generate the docinfo.xml file using these informations, >>>> and Voila! :) >>>> Tested on xml and pdf files. There are some sample available at: >>>> https://github.com/aerostitch/**asciidoc-tools/tree/dev/**samples<https://github.com/aerostitch/asciidoc-tools/tree/dev/samples> >>>> >>>> If you have remarks, just let me know. >>>> >>>> Regards, >>>> Joseph >>>> >>>> >>>> >>>> On Thursday, May 7, 2009 9:55:16 PM UTC+2, JNeudorf wrote: >>>>> >>>>> One thing I do is use git to auto-generate a table (I call this within >>>>> a Makefile): >>>>> >>>>> git log --date=short --pretty=format:"|%an|%ad|%h|%**s" > 1066s- >>>>> hist.txt >>>>> >>>>> I suppose I can do something similar with "sys:", but haven't quite >>>>> worked that out yet. >>>>> >>>>> >>>>> >>>>> -- > You received this message because you are subscribed to a topic in the > Google Groups "asciidoc" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/asciidoc/KFpEXmdzj_A/unsubscribe. > To unsubscribe from this group and all its topics, 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/groups/opt_out. > > > -- 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/groups/opt_out.
