- From: Jirka Kosek <jirka@kosek.cz>
- Date: Thu, 21 Mar 2013 09:56:19 +0100
- To: Arved Sandstrom <asandstrom2@eastlink.ca>
- CC: public-ppl@w3.org
- Message-ID: <514ACB33.8080205@kosek.cz>
On 21.3.2013 3:02, Arved Sandstrom wrote: > After about 3 hours of reading Saxon Java API docs and hacking, the > closest I ever got was locating the DOMEnvelope class, but evidently > that's not the right thing either. I messed around with PJConverters but > they don't appear to understand DOM Nodes. > > It appears that Saxon passes the FO node tree variable in as a > TinyDocumentImpl, which implements no W3C DOM stuff.This is the nub of > the problem. > > Anyone way more familiar with the Saxon 9 HE Java API who might have > some ideas? Thanks. I think that for such Saxon specific question it will be better to ask at saxon-help mailing list (https://lists.sourceforge.net/lists/listinfo/saxon-help) IIRC Saxon can be configured to operate on DOM trees instead of its TinyTree object model -- then you will not be forced to convert back and forth DOM in order to interface with FOP. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------
Received on Thursday, 21 March 2013 08:56:52 UTC