RE: include results of other pipeline?

I have used viewports extensively in my xproc ebook conv app, but less
advanced as you are attempting here. Still might be worthwhile browsing its
code. It’s a pretty complete application..



https://github.com/grtjn/xproc-ebook-conv



Grtz,

Geert



PS: sorry for mentioning it over and over again.. ;)



*Van:* Erik Siegel [mailto:mailing@xatapult.nl]
*Verzonden:* dinsdag 24 september 2013 18:19
*Aan:* 'Romain Deltour'
*CC:* xproc-dev@w3.org
*Onderwerp:* RE: include results of other pipeline?



Hi Romain,



Thanks, that was exactly what I needed!



Erik



*Van:* Romain Deltour [mailto:rdeltour@gmail.com]
*Verzonden:* dinsdag 24 september 2013 15:00
*Aan:* Erik Siegel
*CC:* xproc-dev@w3.org
*Onderwerp:* Re: include results of other pipeline?



Try with p:viewport :

http://www.w3.org/TR/xproc/#p.viewport



Evaluation of a dynamically constructed pipeline (e.g. from a name
contained in an attribute) is not possible in vanilla XProc, but if you're
fine with sticking to a specific processor (e.g. Calabash) some of them
provide an extension step for that (e.g. cx:eval
http://xmlcalabash.com/docs/reference/cx-eval.html)



Hope this helps,

Romain.



On 24 sept. 2013, at 12:40, "Erik Siegel" <mailing@xatapult.nl> wrote:



Hi,



I cant find the solution for this, maybe somebody can give me a hint?



I need to insert the contents of some other (step) into an XML document at
multiple places. This insertion has parameters/options. Its like an
xinclude but not inserting a straight document, instead inserting the
results of a (sub)pipeline-with options.



So, for instance, in some document i have at multiple places (on different
nesting-levels) an element like <insert:insert option1="..." option2="..."/>



This must call a pipeline(step) with the attributes options1 and options2
passed as its options. The results of this pipeline replace the
<insert:insert> element.

I dont see how I can replace all the insert:insert elements and keep the
original structure intact.



Even better would be that you can specify the name of the pipeline(step) on
the insert:insert element, but I think that's a nogo anyway?



Thanks,

Erik Siegel