On Mon, 26 Mar 2012 10:19:29 +1100 Lex Trotman <[email protected]> wrote:
> Docbook, and therefore asciidoc is a *content* markup, not a > presentation markup. So asciidoc doesn't know anything about fonts or > other presentation information. This is what allows the same content > to be used to generate lots of differing output formats. That's OK...I did few books in LyX/LaTeX which is also mostly content markup, but it's possible to influence presentation as well. > But the docbook "role" attribute is intended to mark items that have > particular semantics. The toolchains usually can be configured to > render these differently, eg in a different font. But you would still > have to do something like that suggested by the dblatex folks to > configure their toolchain to do so, eg something like: I see... > Role can be specified as an attribute on most blocks eg paragraphs and > can be applied to a piece of text within a paragraph with unquoted > quotes, see http://www.methods.co.nz/asciidoc/userguide.html#X51. That would be fine...The manual says: "Quoted text can be prefixed with an attribute list. The first positional attribute (role attribute) is translated by AsciiDoc to an HTML span element class attribute or a DocBook phrase element role attribute.", but it would be nice to have some example for DocBook output. Sincerely, Gour -- To deliver the pious and to annihilate the miscreants, as well as to reestablish the principles of religion, I Myself appear, millennium after millennium. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
