On 06/14/2011 10:15 AM, kalgon wrote: > But then, what is the purpose of extensions? There are several > extensions which generate barcodes (barcode4j, zxing-fop-qrcode)... > so if I follow your reasoning, we should not use those and rather > pre-generate the images and use fo:external-graphic, right?
There isn’t anything in the XSL Recommendation about barcodes, so a barcode extension made sense. True, graphics could have been used, but barcodes make a lot of sense as formatting artifacts as well. The MediaWiki markup for which you’re asking involves headings, paragraphs, and lists, which are already supported by XSL. No extension is needed to provide the functionality. > I don't see what you're talking about FOP supporting natively > MediaWiki. How does it support MediaWiki? It doesn’t. That’s what you are asking for. (Remember that “wiki” is a concept of user-edited Web sites; specific kinds of wiki software use different markup. Wikipedia and the other Wikimedia Foundation sites use software called MediaWiki.) > What I want to do is create an extension which can create a subtree > of the FO tree (and reusing basic nodes like Block, Table, FOText) > but I can't find any documentation explaining how to do that (if it's > possible). I'd prefer an extension doing the wiki->fo transformation > in one pass instead of having to write two XSL's with intermediate > results: > I prefer having a self-contained extension which does all the work > for me. That kind of encapsulated transformation makes a lot of sense. However, like other pre-FO transformations, it does not belong in FOP. FOP starts with XSL FO markup; transformations come before that. ~Chris -- Chris Maden, text nerd <URL: http://crism.maden.org/ > “Before I built a wall I’d ask to know / What I was walling in or out, / And to whom I was like to give offence.” — RF, Mending Wall GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
