- From: Erik Siegel <erik@xatapult.nl>
- Date: Mon, 8 Apr 2024 10:35:25 +0200
- To: 'Ari Nordström' <ari.nordstrom@gmail.com>, "'Kraetke, Martin, le-tex'" <martin.kraetke@le-tex.de>
- Cc: <xproc-dev@w3.org>
- Message-ID: <007701da898f$b6fb92c0$24f2b840$@xatapult.nl>
I usually run Morgana as an external tool in oXygen. That works fine. The problem is of course you can’t set input ports and options in the same flexible way as you can do for XProc 1. A solution I use is that I write a tiny test driver pipeline for the pipeline I’m testing/running, that imports the actual pipeline. It then just invokes this with the correct input port and option settings. Erik From: Ari Nordström <ari.nordstrom@gmail.com> Sent: Friday, 5 April 2024 23:41 To: Kraetke, Martin, le-tex <martin.kraetke@le-tex.de> Cc: xproc-dev@w3.org Subject: Re: oXygen Framework for XProc 3.0 Awesome in any case. We've all been wanting XProc 3.0 support. Thanks a lot. Best, /Ari On Fri, 5 Apr 2024 at 13:13, Kraetke, Martin, le-tex <martin.kraetke@le-tex.de <mailto:martin.kraetke@le-tex.de> > wrote: Hi Erik, I didn't expect that they would implement XProc 3.0 soon and since 26.1 was published a few days before, I didn't download it yet. However, the framework currently only supports editing, but it includes a Schematron file into which I planned to gradually add further checks. Furthermore, I planned to add MorganaXProc to allow executions of pipelines in the editor. However, with this move of the oXygen guys, I'd rather think of contributing to oXygen in any form. Best, Martin -- Martin Kraetke Lead Content Engineer le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 143, Fax +49 341 355356 543 martin.kraetke@le-tex.de <mailto:martin.kraetke@le-tex.de> , http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Geschäftsführer / Managing Directors: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt Am 05.04.2024 um 07:43 schrieb Erik Siegel: > Hi Martin, > > Cool! I also had some framework thingie in oXygen for XProc 3 editing but never published it. > > But... did you notice that oXygen 26.1 supports XProc 3.0 editing now? Or is your framework doing more than just that? > > Regards, > Erik Siegel > >> -----Original Message----- >> From: Kraetke, Martin, le-tex <martin.kraetke@le-tex.de <mailto:martin.kraetke@le-tex.de> > >> Sent: Wednesday, 3 April 2024 19:25 >> To: xproc-dev@w3.org <mailto:xproc-dev@w3.org> >> Subject: oXygen Framework for XProc 3.0 >> >> Hi everyone! >> >> I've created a framework for the oXygen XML editor to facilitate the editing of >> XProc 3.0 pipelines. It's just a fresh start so don't expect too much. >> >> https://github.com/transpect/xproc3kit >> >> Feedback is always welcome in the Issues section of the repository. >> >> Best, Martin >> >> Am 18.03.2024 um 15:53 schrieb Norm Tovey-Walsh: >>> Krzysztof Nowak <krzysztof.nowak@ijp.pan.pl <mailto:krzysztof.nowak@ijp.pan.pl> > writes: >>>> Just for my reference, is this what the docs >> (https://spec.xproc.org/3.0/xproc/#p.choose) are talking about in the paragraph >> that starts with "The outputs of the p:choose are taken from the outputs..."? >>> >>> Precisely. Beware that the rules are similar, but not exactly the same, in 3.0. >>> >>>> Anyway, thanks a ton again! >>> >>> Happy to help. >>> >>> Be seeing you, >>> norm >>> >>> -- >>> Norm Tovey-Walsh <ndw@nwalsh.com <mailto:ndw@nwalsh.com> > >>> https://norm.tovey-walsh.com/ >>> >>>> On the other hand, you have different fingers. >
Received on Monday, 8 April 2024 08:35:50 UTC