[...] >> b. FOP specifies it in the XSL stylesheets which can't be done from >> asciidoc > > > How does FOP know which parts need columns ? Seems impossible to indicate > after AsciiDoc using XSL. >
Well default sections title-page, toc, front, body, back, index can each have a different page master with the standard XSL. Thats a bit coarse but built in. Default toc and index is in fact two column. With an XSL customisation you could use the role to select use of a different page master I think, but as I repeatedly say I'm no XSLspurt. > > >> c. HTML specifies it in CSS3, the only way that *might* be able to be >> done from asciidoc, but only for CSS3 compliant browsers. > > > Right, but for HTML output using columns may not be as desirable as for PDF > or print output. Still, it might be useful in some cases. > No, only for my continued campaign for keeping web site text to 40em wide. > > >> Two out of three current backend toolchains cannot support such markup. >> >> Using this feature makes the document backend specific anyway so the >> techniques such as passthrough of ODT or backend specific markup can >> be used. Any technique that can be done in the backend and does not >> require asciidoc support would be ok. > > > So what I propose is acceptable ? But documented outside the scope of > AsciiDoc so potentially implemented differently in another backend ? :-/ > 1. it needs to be documented 2. since it isn't implemented in other backends it should give an error, which is correct behavior when a feature that is not available is used. 3. this is why presentation markup should be kept out of asciidoc, each backend (and for docbook each toolchain) has its own capabilities and features. There is no standard set of presentation features. 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.
