- From: Paul Tyson <phtyson@sbcglobal.net>
- Date: Mon, 18 Aug 2014 21:11:04 -0500
- To: XProc Dev <xproc-dev@w3.org>
Thanks, Norm. Works for me. Specifically, p:data for plain text (#154) and p:www-form-urlencode for values with '+' (#163). Regards, --Paul On Sun, 2014-08-17 at 15:14 -0500, Norman Walsh wrote: > Hi folks, > > I've quietly published XML Calabash 1.0.19-b1. You can get it from > http://xmlcalabash.com/download/calabash-1.0.19-b1-95.jar or > http://xmlcalabash.com/download/calabash-1.0.19-b1-95.zip but > I haven't added any links to those files anywhere yet. > > Consider it a test release. Feedback most humbly solicited. > > Here's what I think I did: > > * Fix issue #162 make sure descendants are copied correctly. The > pxp:set-base-uri step was completely broken. > > * Replaced RelevantNodes with AxisNodes. This is an intentionally > breaking change in the internal API. It shouldn't effect you unless > you've written your own extension step that uses RelevantNodes. If > you've been using RelevantNodes, you're probably not getting the > results you expect, even if the differences are uncommon. > > * Add support for producing an AsciiDoc test report. > > * Fixed bug in the p:xsl-formatter step where the PDF file wasn't > getting closed properly. > > * I reverted a change where I'd removed an exception for the case > where you attempt to read from a directory that wasn't actually > a directory. > > * Fix issue #163 by encoding spaces as + and encoding + as %2B > > * Attempted to clean up some issues with respect to content-type > in p:data. Maybe fix issue #154? > > * Added a cx:version attribute to p:validate-with-xml-schema to > select a specific schema version. > > * Made failure to validate a requested extension function more > obvious (bumped log level to info). > > * Made application/pdf the default content type for the CSS > formatting step. > > * Copy antlib.xml into jar file to fix issue #157 > > > Be seeing you, > norm >
Received on Tuesday, 19 August 2014 02:12:50 UTC