Re: FO->Area as XSLT extension function

Keep me advised if any problems. I'm going to continue working on 
various aspects of it.

I'll be interested to see the XSLT experts here (which I suspect is 
everyone except me) develop and refine the usage pattern for the 
extension function. One immediate proof-of-concept (POC) pattern, I 
would guess based on discussion to date, is then to use document() with 
XPath to check one or more settings. Again speculating out loud, we have 
access to both the FO node tree as an XSLT variable at that point, and 
in theory also the FOP Intermediate Format (IF) node tree if we cared to 
obtain it. So either/or would be modifiable (new variable and all that, 
but that's the idea).

Am I off base here?

I can easily enough modify the extension function to specify input and 
output modes for FOP runs. Logical outputs are IF (1st run) and PDF (2nd 
run). Inputs can be either FO or IF in our scenario.

Just let me know where to put the POC NetBeans project. Over the years - 
I may date myself here - I've used SCCS, RCS, CVS, Bitkeeper, Darcs, 
SourceSafe, DCVS, Mercurial, Git, Perforce, SVN, IBM ClearCase.. - you 
get the idea. :-) I'd myself prefer accessing the W3C Hg directly: I am 
a non-fan of git.

Building on what's already been mentioned (by you I think, Tony) this is 
a good opportunity to look at the Apache FOP area tree Intermediate 
Format (I like the name), and see if we can't work towards a somewhat 
standardized spec for it. I can easily subclass the FOP area tree 
renderer to provide a W3C PPL WG area tree format renderer.

Having gone through this initial exercise I am starting to come into the 
fold of controlling the feedback through XSLT. Fact is, the ideas I had 
are well within the grasp of a competent coder today. It's exposing 
similar ability to XSLT that makes sense.

Arved

On 03/17/2013 10:06 AM, Tony Graham wrote:
> On Sun, March 17, 2013 1:56 am, Arved Sandstrom wrote:
>> Ok, I've got product, just not sure how to best disseminate. So I've
>> attached stuff. I suspect that my NetBeans project I'll want to get into
>> Mercurial or whatever it was that we set up.
> Great stuff.  Thanks.  I've downloaded it all, and I'll try it later today.
>
> Where to put it is an interesting question.  Or would have been.  Because
> it's 'real code', the (currently) natural choice would be to put it on
> GitHub so others can easily contribute, but we also have the Mercurial
> repository at the W3C onto which I was about to put the previous XSL-FO
> 2.0 WD.  However, it appears that we can have our cake and eat it too
> since there's a 'hg-git' plugin for bridging between Mercurial and Git so
> that we could easily mirror the Mercurial repository on GitHub [2].  The
> only issue then would be deciding what to do if a non-member makes a pull
> request on the GitHub project, since we can only accept stuff from people
> who've agreed to the contributor's agreement (or whatever it's called).
>
> Regards,
>
>
> Tony.
>
> [1] http://hg-git.github.com/
> [2] http://hgtip.com/tips/advanced/2009-11-09-create-a-git-mirror/
>
>

Received on Sunday, 17 March 2013 16:46:34 UTC