On 06/27/11 10:55:34, Lex Trotman wrote: > > > > Therefore, the short-term solution would be to figure out > > how to pass a new language definition to dblatex. That will > > Configuring latex, good luck and may god bless all who sail in her ... > thats (un)fortunately beyond the scope of this ML.
Indeed. For me, that particular ship can seldom make it out of the harbor. :) > giyf http://sourceforge.net/apps/mediawiki/xslthl/index.php?title=Main_Page > > and several how-to pages come up in a search. Seems to need a java > xslt processor (xalan or saxon) but that should be ok if you can run > fop. Thanks, here's a promising how to: http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/ > Can't, docbook doesn't have formatting, it is content markup not > presentational markup. Thats why you have to play with the backends. > Of course thats also why you can use differing backends from the same > source :-) Understood, I was thinking of augmenting the Docbook XML along the lines that you suggest below. > IIUC source-highlight is configurable. Off the top of my head I would > suggest that you define roles on <phrase> entities wrapping bits of > source. That can be used to control xsl processing, see > http://www.sagehill.net/docbookxsl/AddNewTemplate.html#AttValueFormatting > so you can translate it into fo instructions for fop and probably > latex instructions for dblatex. And for HTML the role gets added as a > class (with the right option set) so you can use CSS to style the > HTML, which is better than the hard coded way it is done by > source-highlight HTML. Yes, I haven't looked in detail how to configure source highlight in that way. -- 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.
