On Sun, Mar 25, 2012 at 07:19:29PM EDT, Lex Trotman 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. Each output > processor can perform its own formatting, but each has also chosen its > own method of customisation. So Asciidoc would have to have special > customisations for each toolchain if it was to specify presentation > and that is beyond its scope. [..] I'm sorry but although I understand (and like everybody else approve of) the concept of separation between structure and presentation... where _users_ of asciidoc are concerned, this answer is not satisfactory. When I'm writing a document in English comprising quotes from say Russian and ancient Greek, I need to know how I can switch to a quality Russian font and then back to my standard English font, and then switch again to a nice Greek font. I don't want as Gour just did to have to scour the latex, docbook, xetex, dblatex, etc. etc. for a solution. These use cases should be documented in the asciidoc manual and basic working examples provided for asciidoc to be credible. CJ -- Oh My God!!! Larry is back! -- 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.
