Since I'm generating Kindle books (which require non-javascript clickable indexes) which requires a toolchain of - a2x -d book -f xhtml...
So this means hacking up XSL... Ugh... Looks like "role=..." gets propagated to the .xml file as in the form... <informaltable role="yellow-background" frame="all" rowsep="1" colsep="1"> So XSL has to be written to transform each "role" in the final HTML5. Several questions... as I tend to avoid XSL whenever possible... 1) ../docbook-xsl/common.xsl is where all the table transforms live... Let me know the correct incantation to effect <td> background color. I've tried many experiments and the correct syntax escapes me. like... <xsl:param name="table.cell.background.color" select="'red'"/> <xsl:param name="table.cell.color" select="'red'"/> 2) Modifying ../docbook-xsl/common.xsl is a bad idea since it can be overwritten during updates. Let me know the preferred way to add a user defined .xsl file. 3) Let me know the preferred way to reference custom .xsl files in the a2x toolchain. Thanks. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
