W3C home > Mailing lists > Public > xproc-dev@w3.org > May 2009

Re: xproc use case, demonstrator

From: Dave Pawson <dave.pawson@gmail.com>
Date: Fri, 22 May 2009 12:20:30 +0100
Message-ID: <711a73df0905220420j6634f950k5bed649a831c9535@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: XProc Dev <xproc-dev@w3.org>
2009/5/22 Norman Walsh <ndw@nwalsh.com>:

> I have every confidence it can, but I can't for the life of me see
> what that ant script does. What is "antvars.py" and what are the
> expected properties?

I've put all the properties(vars) in an external / included file
which is a Sun spec in plain text, hence I've parsed them
using a Python script. I could do it with xslt 2.0 though.

Just need some way to check that I've defined all the properties
before I use them, since ant gaily uses ${varname} as a filename (grrr)

> You seem to be doing the following:
>  Run antvars.py to produce testvars.xml
>  Run testvars.xml *with* ant

yes, How to write some xml ...
then run that file as an xproc step!!
can xproc recurse!

>  Delete testvars.xml
>  Run XSLT over input/build.xml to produce testvars.xml
>  Run testvars.xml *with* ant *again*

different testvars.xml this time
Same requirement though.

> That seems like a very strange Ant setup. What on earth is going on
> that requires that much complexity?

Scratching an itch. See above on checking vars.

>> Might prove a useful demonstrator since
>> it is non-trivial?
> Sure. See also
> http://norman.walsh.name/2009/03/26/xprocWithXProc

Yes... I note your caveats too Norm <grin/>

More the merrier?


Dave Pawson
Docbook FAQ.
Received on Friday, 22 May 2009 11:21:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:05 UTC