Thanks for the explanation about MediaWiki: the term natively led me to think that FOP already had support for MediaWiki syntax. As I was talking about an extension, I didn't see how it could be done natively.
So if the WIKI->FO-XML transformation does not belong to FOP, it surely belongs to the transformation part which comes before rendering. But then, I should use Saxon or Xalan specific extensions or does javax.xml.transform provide an unified way to do such a thing? I have currently no idea on how to do that but I suppose the wiki parsing routine will have to be called from inside the stylesheet and I have had bad experiences trying to call java code from xslt. And if javax.xml.transform does not provide a standard way to do that, I will have to create specific extensions for each xslt library (Saxon and Xalan). If I could do it directly through a FOP extension, I would not have those problems. So, now that I understand that such a processing is better done outside FOP, do you think there's a way I could do it inside though an extension? :-) If somebody has a simple example of how an extension could programmatically create a FOText inside a Block, I think I could handle the rest. Regards, Xavier Christopher R. Maden wrote: > > 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] > > > -- View this message in context: http://old.nabble.com/FOP-Extension-to-handle-Wiki-Syntax-tp31841403p31843733.html Sent from the FOP - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
