Re: Transforming the c:param-set document from the parameters port

The wonderful thing about posting to a mailing list is that it so often 
inspires you to see the obvious solution immediately /after/ you hit 
Send. Occasionally, the act of composing the message inspires me to see 
the solution before I hit Send, but not this time.

Obviously, I just need to explicitly declare the result of my 
transformation as the input for the parameters port for any subsequent 
xslt steps or their wrappers:

      <p:xslt>
         <p:input port="parameters" kind="parameter">
             <p:pipe port="result" step="param-fixup"/>
         </p:input>
...

I'd been trying to do that for p:group, but only a step can have a 
parameters port.

Regards,
David

On 10/14/17 11:03 PM, David Cramer wrote:
> Some time ago, I learned on this list how to fetch values from the 
> c:param-set that comes in on the parameter port to use in p:variable 
> values in my pipeline: 
> https://lists.w3.org/Archives/Public/xproc-dev/2012May/0005.html
>
> Now I'm attempting to transform that c:param-set before my xslt steps 
> consume it. Transforming the c:param-set is easy enough by taking as 
> input the result of the Geert Josten's ut:parameters utility step: 
> https://github.com/grtjn/xproc-ebook-conv/blob/master/src/nl/grtjn/xproc/util/utils.xpl#L374
>
> However, once the c:param-set is transformed, I haven't figured out 
> how to make subsequent steps in the pipline use the manipulated version.
>
> I could manipulate the parameters in the scripts that call calabash or 
> in the xslts, but it feels like I should be able to run the 
> c:param-set thorough an xslt and then use the result of that in the 
> rest of my pipline.
>
> Is this possible?
>
> Btw., I'm running xmlcalabash-1.1.16-97
>
> Regards,
> David
>
>