- From: James Fuller <jim@webcomposite.com>
- Date: Mon, 2 Mar 2015 16:36:25 +0100
- To: Tony Graham <tgraham@mentea.net>
- Cc: XProc Comments <public-xml-processing-model-comments@w3.org>
Hello Tony, I think the convention today is to use try/catch to trap xsl:message ... but yes an apropos use case to consider; THANKS! J On 2 March 2015 at 15:37, Tony Graham <tgraham@mentea.net> wrote: > On Mon, March 2, 2015 12:57 pm, James Fuller wrote: >> as per ACTION: A-265-01 >> (http://www.w3.org/2015/02/25-xproc-minutes.html#action01) ... > ... >> On first pass an error port on an atomic step might be an odd beast in >> xproc. The p:exec step defines an errors output port which would help >> diagnose unexpected errors ... or partial errors where some processing >> was possible. Similarly, I could imagine an errors port from steps >> that are facade into other languages, such as p:xslt or p:xquery. But > > Yes, just yesterday I was looking at how to get xsl:message output from > the XSLT in the pipeline in stf (https://github.com/MenteaXML/stf). > Couldn't get it to work. > > Regards, > > > Tony. > >
Received on Monday, 2 March 2015 15:36:52 UTC