On 30 March 2012 08:46, Gary Funck <[email protected]> wrote: > On 03/30/12 08:17:16, Stuart Rackham wrote: >> [...] >> linkcss is for html5 and xhtml11 backends (not docbook). > > OK. > > Perhaps the issue that I posted as a follow up to the > thread is unrelated to the original thread. I thought > it might be because I have a left over docbook-xsl.css file > that hangs around after I run 'make'. My make file will > generate both a .pdf via and .html rendering of the > original asciidoc document. I see that the .html document > does refer to docbook-xsl.css: > <link rel="stylesheet" type="text/css" href="docbook-xsl.css" /> > It looks that the web browser will need to find that .css file > if it is going to properly render the .html file?
Hi Gary, Indeed it will. > > My .html file 'make' rule looks like this: > > # Delete revision history, collaborators, "produced by pdflatex" logo. > # Enable inclusion of a table of figures and tables. > DBLATEX_OPTS=--dblatex-opts="-P latex.output.revhistory=0 \ > -P latex.class.options=letterpaper \ > -P doc.collab.show=0 -P doc.publisher.show=0 \ > -P doc.lot.show=figure,table" > [...] > > .txt.html: > a2x -f xhtml $(DBLATEX_OPTS) $< Xhtml is generated by xsltproc not dblatex so there is no point in putting dblatex opts on -f xhtml > > It seems that a local copy of the docbook-xsl.css file > might be needed, and therefore I'll need to have it > available to render the .html file, but it also seems > that if an older copy of docbook-xsl.css is present > that a2x will not overwrite it with a newer version > of docbook-xsl.css if that newer file exists in > the asciidoc distribution? See the a2x manpage resources section, the first place it looks for resources is the source directory, which in your case is also your output directory so after the first time nothing is updated. Better to put your output in a different directory from the source to avoid such confusion. There is no way of embedding the css when using xsltproc to generate the xhtml since xsltproc just doesn't do it. I suspect you have confused the two ways you can generate xhtml from asciidoc input: 1. using asciidoc - which can embed resources when instructed by linkcss 2. using a2x - which uses asciidoc to generate docbook and then uses xsltproc to generate xhtml, which is what you are doing Cheers Lex -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
