Activity for MorganaXProc-IIIse

xml-project.com modified ticket #222

xml-project.com — Sun, 19 Apr 2026 07:09:01 -0000

with multiple outputs will fail if not all outputs are referenced

xml-project.com posted a comment on ticket #222

xml-project.com — Sun, 19 Apr 2026 07:09:01 -0000

The problem appears also with p:for-each. Fixed with 1.8.7 Thank you for reporting this to Boris.

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.7/MorganaXProc-IIIse-1.8.7.zip

MorganaXProc-IIIse — Sun, 19 Apr 2026 07:08:02 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.7/MorganaXProc-IIIse-1.8.7-sources.zip

MorganaXProc-IIIse — Sun, 19 Apr 2026 07:08:02 -0000

Boris Lehečka created ticket #222

Boris Lehečka — Fri, 17 Apr 2026 22:20:35 -0000

with multiple outputs will fail if not all outputs are referenced

xml-project.com modified ticket #221

xml-project.com — Wed, 15 Apr 2026 16:36:03 -0000

Remove __MACOSX metadata from releases

xml-project.com posted a comment on ticket #221

xml-project.com — Wed, 15 Apr 2026 16:36:03 -0000

Implemented with 1.8.6

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.6/MorganaXProc-IIIse-1.8.6-sources.zip

MorganaXProc-IIIse — Wed, 15 Apr 2026 16:32:48 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.6/MorganaXProc-IIIse-1.8.6.zip

MorganaXProc-IIIse — Wed, 15 Apr 2026 16:32:48 -0000

aronadaal posted a comment on ticket #221

aronadaal — Fri, 27 Mar 2026 08:39:45 -0000

Great, thank you very much! Of course, I can delete the data myself—you’re right. But data like that shouldn’t be included in a release in the first place. It should only contain data that’s actually related to the software. We recommend Morgana to our stakeholders. And I’ve been asked about this folder so many times.

xml-project.com modified ticket #221

xml-project.com — Wed, 25 Mar 2026 07:02:02 -0000

Remove __MACOSX metadata from releases

xml-project.com posted a comment on ticket #221

xml-project.com — Wed, 25 Mar 2026 07:02:02 -0000

I will try to update my distribution process in the future, but I don't see, why the existence of the "MACOS"-folder is a problem. You can either ignore it or delete it.

aronadaal created ticket #221

aronadaal — Tue, 24 Mar 2026 19:34:12 -0000

Remove __MACOSX metadata from releases

xml-project.com modified ticket #214

xml-project.com — Sun, 15 Mar 2026 08:40:29 -0000

Error message suggestion: make -> convert

xml-project.com posted a comment on ticket #214

xml-project.com — Sun, 15 Mar 2026 08:40:29 -0000

Done with 1.8.4

xml-project.com modified ticket #219

xml-project.com — Sun, 15 Mar 2026 08:40:02 -0000

Regression in 1.8.2?

xml-project.com posted a comment on ticket #219

xml-project.com — Sun, 15 Mar 2026 08:40:02 -0000

Fixed with 1.8.4

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.4/MorganaXProc-IIIse-1.8.4.zip

MorganaXProc-IIIse — Sun, 15 Mar 2026 08:38:03 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.4/MorganaXProc-IIIse-1.8.4-sources.zip

MorganaXProc-IIIse — Sun, 15 Mar 2026 08:38:03 -0000

xml-project.com modified ticket #214

xml-project.com — Thu, 12 Mar 2026 06:50:21 -0000

Error message suggestion: make -> convert

xml-project.com modified ticket #220

xml-project.com — Thu, 12 Mar 2026 06:36:21 -0000

Support exproc steps

xml-project.com posted a comment on ticket #220

xml-project.com — Thu, 12 Mar 2026 06:36:20 -0000

Both exproc steps are supported by MorganaXProc-IIIee: ex:epubcheck since 1.7.6, ex:expand-templates since 1.8. There are no plans to bring pro-features to the standard edition.

John Nicholas created ticket #220

John Nicholas — Wed, 11 Mar 2026 13:32:50 -0000

Support exproc steps

David J Birnbaum posted a comment on ticket #219

David J Birnbaum — Thu, 05 Mar 2026 15:54:50 -0000

Thanks, @xml-project-com, for the quick response! I'll back up to 1.8 and watch for 1.8.3.

xml-project.com modified ticket #219

xml-project.com — Thu, 05 Mar 2026 15:53:06 -0000

Regression in 1.8.2?

xml-project.com posted a comment on ticket #219

xml-project.com — Thu, 05 Mar 2026 15:53:06 -0000

Thanks David. That is actually a regression. I changed an interface, but forgot to recompile and pack the MarkupBlitzConnector. Will be fixed in next release.

David J Birnbaum created ticket #219

David J Birnbaum — Thu, 05 Mar 2026 15:40:25 -0000

Regression in 1.8.2?

xml-project.com modified ticket #218

xml-project.com — Sun, 01 Mar 2026 08:13:23 -0000

Question about p:xslt secondary document serialization maps

xml-project.com posted a comment on ticket #218

xml-project.com — Sun, 01 Mar 2026 08:13:23 -0000

I think we can close this.

Sy Holmes posted a comment on ticket #218

Sy Holmes — Tue, 24 Feb 2026 14:43:07 -0000

Oh! That makes a lot of sense. I thought it was handled according to the special rules for casting xs:QName section (https://spec.xproc.org/lastcall-2025-03/head/xproc/#qname-handling) and had (obviously mistakenly) ignored that as a way of troubleshooting. As an additional convenience, if the specified sequence type of an option or a variable is a map with xs:QName keys (map(xs:QName, …)), the supplied map value is processed specially. This makes it possible to pass in maps using (easier to write)...

xml-project.com modified ticket #218

xml-project.com — Tue, 24 Feb 2026 14:42:17 -0000

Question about p:xslt secondary document serialization maps

xml-project.com posted a comment on ticket #218

xml-project.com — Tue, 24 Feb 2026 14:16:49 -0000

The problem comes from tyring to get the values via string. The serialization map is defined as map{xs:QName(), item*) Therefor you do not get any value for "method" because the key is not present. If you use xs:QName('method') instead, you get the expected results. Hope that helps.

Sy Holmes created ticket #218

Sy Holmes — Mon, 23 Feb 2026 20:32:44 -0000

p:xslt secondary document serialization map entries empty when accessed as map

xml-project.com modified ticket #216

xml-project.com — Mon, 16 Feb 2026 07:49:44 -0000

Feature request: allow relative paths in XML catalogs

xml-project.com posted a comment on ticket #216

xml-project.com — Mon, 16 Feb 2026 07:49:44 -0000

Implemented in 1.8.2

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.2/MorganaXProc-IIIse-1.8.2-sources.zip

MorganaXProc-IIIse — Mon, 16 Feb 2026 07:49:02 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8.2/MorganaXProc-IIIse-1.8.2.zip

MorganaXProc-IIIse — Mon, 16 Feb 2026 07:49:02 -0000

xml-project.com modified ticket #216

xml-project.com — Fri, 13 Feb 2026 07:26:08 -0000

Feature request: allow relative paths in XML catalogs

xml-project.com modified ticket #217

xml-project.com — Fri, 13 Feb 2026 07:25:38 -0000

Pipelines source files with UTF-8 BOM generate an error

xml-project.com posted a comment on ticket #217

xml-project.com — Fri, 13 Feb 2026 07:25:38 -0000

Done!

Micha Huebert posted a comment on ticket #216

Micha Huebert — Mon, 09 Feb 2026 08:31:02 -0000

Hi Achim, thanks for the explanation and for putting this on your Morgana todo list. Regards, Micha

xml-project.com modified ticket #217

xml-project.com — Sat, 07 Feb 2026 07:46:18 -0000

Pipelines source files with UTF-8 BOM generate an error

xml-project.com modified ticket #217

xml-project.com — Sat, 07 Feb 2026 07:45:08 -0000

Error when XPL has UTF-8 BOM

xml-project.com modified ticket #217

xml-project.com — Sat, 07 Feb 2026 07:44:29 -0000

Error when XPL has UTF-8 BOM

xml-project.com posted a comment on ticket #217

xml-project.com — Sat, 07 Feb 2026 07:44:29 -0000

Right, you need to remove the BOM first or use a editor setting not creating a BOM in the first place. I should state that more explictly in the documentation.

John Nicholas created ticket #217

John Nicholas — Fri, 06 Feb 2026 17:54:49 -0000

Error when XPL has UTF-8 BOM

xml-project.com modified ticket #216

xml-project.com — Fri, 06 Feb 2026 17:42:23 -0000

Feature request: allow relative paths in XML catalogs

xml-project.com posted a comment on ticket #216

xml-project.com — Fri, 06 Feb 2026 17:42:06 -0000

Hi Micha, on research I found out, I missunderstand your request. The problem with MorganaXProc-III is that the EntityResolver allways returns absolute URIs for systemId. Saxon and XMLCalabash3 use an advanced version (EntityResolver2) giving acces to the original systemID. I will try to implement this. Greetings from Germany, Achim

xml-project.com posted a comment on ticket #216

xml-project.com — Fri, 06 Feb 2026 12:34:31 -0000

Hi Micha, this is strange. As far as I know, Saxon, XMLCalabash 3 and MorganaXProc-III use the same catalog resolver software (XML Resolver) So what work for them should work for MorganaXProc-III. What error message do you get? Greetings from Germany, Achim

Micha Huebert created ticket #216

Micha Huebert — Fri, 06 Feb 2026 11:15:32 -0000

Feature request: allow relative paths in XML catalogs

xml-project.com modified ticket #215

xml-project.com — Sat, 24 Jan 2026 08:57:59 -0000

Question about name attribute in error document

A Galtman posted a comment on ticket #215

A Galtman — Fri, 23 Jan 2026 16:00:45 -0000

Thanks for explaining. It makes more sense to me now. My expectation was formed by the sentence in the specification that says, "The name and type attributes identify the name and type, respectively, of the step which failed." However, a paragraph earlier in the document uses the word "should" in the sentence, "In order to facilitate some modicum of interoperability among processors, errors that are reported on the error input port of a p:catch should conform to the format described here." I guess...

xml-project.com posted a comment on ticket #215

xml-project.com — Fri, 23 Jan 2026 15:49:16 -0000

The error document identifies the type, line, and column of the element, as I expected. But the name says name="valueproducer-add-attr-Q{}attribute-value" instead of name="add-attr". The error message is more specific than just "add-attr". It tells you that the error occurred producing the value of "Q{}attribute-value" in step "add-attr". This is a result of my implementation and I decided that its better than to leave out the "name"-attribute (which is optional...

A Galtman created ticket #215

A Galtman — Fri, 23 Jan 2026 15:38:45 -0000

Question about name attribute in error document

xml-project.com modified ticket #214

xml-project.com — Fri, 23 Jan 2026 15:29:24 -0000

Error message suggestion: make -> convert

xml-project.com posted a comment on ticket #214

xml-project.com — Fri, 23 Jan 2026 15:29:24 -0000

A quick look at the code base shows, that I use "make" and "convert" on multiple occasion with no real semantic difference. So it make sense to harmonize message.

xml-project.com modified ticket #213

xml-project.com — Fri, 23 Jan 2026 15:13:41 -0000

p:catch catches an error despite non-matching code

A Galtman posted a comment on ticket #213

A Galtman — Fri, 23 Jan 2026 15:11:37 -0000

Sorry, my mistake. I forgot that the command-window output for a raised error is the same error document as a caught error. I was comparing with XML Calabash, and there the command-window output is different for a raised error vs. caught error. You can close this ticket.

A Galtman created ticket #214

A Galtman — Fri, 23 Jan 2026 15:06:31 -0000

Error message suggestion: make -> convert

xml-project.com posted a comment on ticket #213

xml-project.com — Fri, 23 Jan 2026 15:03:32 -0000

Would you mind to explain. The result looks correct to me. Use:

and you still get the same result. My conclusion: p:catch isn't fired.

A Galtman created ticket #213

A Galtman — Fri, 23 Jan 2026 14:53:09 -0000

p:catch catches an error despite non-matching code

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8/MorganaXProc-IIIse-1.8.zip

MorganaXProc-IIIse — Thu, 15 Jan 2026 16:25:37 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.8/MorganaXProc-IIIse-1.8-sources.zip

MorganaXProc-IIIse — Thu, 15 Jan 2026 16:25:37 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.6/MorganaXProc-IIIse-1.7.6.zip

MorganaXProc-IIIse — Sat, 20 Dec 2025 12:58:04 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.6/MorganaXProc-IIIse-1.7.6-sources.zip

MorganaXProc-IIIse — Sat, 20 Dec 2025 12:58:04 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.4/MorganaXProc-IIIse-1.7.4.zip

MorganaXProc-IIIse — Sun, 16 Nov 2025 16:17:03 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.4/MorganaXProc-IIIse-1.7.4-sources.zip

MorganaXProc-IIIse — Sun, 16 Nov 2025 16:17:03 -0000

xml-project.com modified ticket #212

xml-project.com — Wed, 29 Oct 2025 08:48:50 -0000

Error running on very large file (800MB)

xml-project.com posted a comment on ticket #212

xml-project.com — Wed, 29 Oct 2025 08:48:50 -0000

Thank you, Mark.

Mark Dunn posted a comment on ticket #212

Mark Dunn — Wed, 29 Oct 2025 08:40:52 -0000

Thanks very much Achim, we will try this. I think we can close the ticket as resolved.

xml-project.com posted a comment on ticket #212

xml-project.com — Wed, 29 Oct 2025 08:38:41 -0000

Given this constraint and the nature of the package content, would it still be worth switching up to 1.7.2? I can also reqest an increase to the size of java.io.tmpdir I think you need to increase the size of java.io.tmpdir: If you do not use an exclude- or include-filter on p:unarchive, all entries associated with Binary content-types will be written to this folder. So you need enough space for them. Switching to 1.7.2 makes most sense, if you have more than on p:unarchive or an iteration over a...

Mark Dunn posted a comment on ticket #212

Mark Dunn — Wed, 29 Oct 2025 08:30:29 -0000

Thanks Achim, this sounds like the right explanation. Most of the package is a few videos, each of 100-200MB in size. The java.io.tmpdir has a maximum capacity of 2GB so it's likely that this was getting full at the time this job was run. Given this constraint and the nature of the package content, would it still be worth switching up to 1.7.2? I can also reqest an increase to the size of java.io.tmpdir

xml-project.com posted a comment on ticket #212

xml-project.com — Wed, 29 Oct 2025 08:05:22 -0000

Hi Mark, that is difficult to say as I do no have any expirience with RedHat Linux. It would be helpful to know more details about your pipeline and the content of the ZIP documents. My guess would be, that the ZIP contains a lot of images, PDFs etc. This is because MorganaXProc-III handles the different document types defined by XProc in different ways: XML, XHTML, JSON and Text are extracted from the ZIP, parsed and held as an in memory representation. So here is no disk space involved. When it...

Mark Dunn created ticket #212

Mark Dunn — Tue, 28 Oct 2025 14:55:44 -0000

Error running on very large file (800MB)

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.2/MorganaXProc-IIIse-1.7.2-sources.zip

MorganaXProc-IIIse — Wed, 15 Oct 2025 16:52:04 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.2/MorganaXProc-IIIse-1.7.2.zip

MorganaXProc-IIIse — Wed, 15 Oct 2025 16:52:04 -0000

xml-project.com modified ticket #3

xml-project.com — Thu, 18 Sep 2025 06:43:06 -0000

Attribute "[p:]message" with AVT does not work on certain constructs

xml-project.com posted a comment on ticket #3

xml-project.com — Thu, 18 Sep 2025 06:43:06 -0000

Fixed with 1.7.0

A Galtman posted a comment on ticket #210

A Galtman — Sun, 14 Sep 2025 11:32:31 -0000

Thanks a lot! I confirmed that I no longer see the error in my real use case.

xml-project.com modified ticket #210

xml-project.com — Sun, 14 Sep 2025 08:37:13 -0000

Exception using p:xquery

xml-project.com posted a comment on ticket #210

xml-project.com — Sun, 14 Sep 2025 08:37:13 -0000

Fixed with 1.7.1.

xml-project.com modified ticket #211

xml-project.com — Sun, 14 Sep 2025 08:36:32 -0000

Typo in error message

xml-project.com posted a comment on ticket #211

xml-project.com — Sun, 14 Sep 2025 08:36:32 -0000

Thanks for this! Fixed with 1.7.1

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.1/MorganaXProc-IIIse-1.7.1.zip

MorganaXProc-IIIse — Sun, 14 Sep 2025 08:35:03 -0000

MorganaXProc-IIIse released /MorganaXProc-IIIse-1.7.1/MorganaXProc-IIIse-1.7.1-sources.zip

MorganaXProc-IIIse — Sun, 14 Sep 2025 08:35:03 -0000

xml-project.com posted a comment on ticket #210

xml-project.com — Sat, 13 Sep 2025 13:19:41 -0000

May be it helps to know, that the September release is scheduled for tomorrow (or Monday, if I try to include Saxon 12.9).

A Galtman posted a comment on ticket #210

A Galtman — Sat, 13 Sep 2025 13:16:20 -0000

Thank you for your comments and future fix. In the meantime, I may be able to work around this by using p:set-properties to restore the base URI before calling p:xquery. (Using the c:xquery document directly doesn't work in my case due to some requirements regarding escaping.)

xml-project.com modified ticket #210

xml-project.com — Sat, 13 Sep 2025 11:50:12 -0000

Exception using p:xquery

xml-project.com posted a comment on ticket #210

xml-project.com — Sat, 13 Sep 2025 11:50:12 -0000

Thanks for this: The reported NullPointerException is a combination of two bugs: * p:cast-content-type does not copy the base-uri from source to result * p:xquery does not change query document for missing base-uri. The workaround for the problem is, as you said, just to leave out the p:cast-content-type in the first example. There is currently no work-around for the second problem with the xml-wrapped query. This will be fixed in the next release. Hint (as I do not known your use case exactly):...

xml-project.com modified ticket #211

xml-project.com — Sat, 13 Sep 2025 08:28:59 -0000

Typo in error message

xml-project.com posted a comment on ticket #211

xml-project.com — Sat, 13 Sep 2025 08:28:59 -0000

Thanks for this! This mistake is a bit awkward.

A Galtman created ticket #211

A Galtman — Fri, 12 Sep 2025 17:36:52 -0000

Typo in error message

A Galtman created ticket #210

A Galtman — Fri, 12 Sep 2025 17:32:52 -0000

Exception using p:xquery

xml-project.com modified ticket #209

xml-project.com — Tue, 09 Sep 2025 18:19:51 -0000

p:validate-with-json-schema fails to XVRL report w/detections on invalid input

John Nicholas posted a comment on ticket #209

John Nicholas — Tue, 09 Sep 2025 16:19:42 -0000

Here is the output when using json-schema-validator 1.0.79 ================================= MorganaXProc-IIIse 1.6.15 Copyright 2011-2025 by Achim Berndzen ================================= Json schema validation using networknt/json-schema-validator. Copyright (c) Network New Technologies Inc. 2025-09-09T12:15:12.25-04:00

xml-project.com modified ticket #208

xml-project.com — Tue, 09 Sep 2025 13:28:22 -0000

Unable to set Saxon's "expandAttributeDefaults" config option

xml-project.com posted a comment on ticket #208

xml-project.com — Tue, 09 Sep 2025 13:28:22 -0000

I think we can close this.

xml-project.com modified ticket #209

xml-project.com — Tue, 09 Sep 2025 13:27:47 -0000

p:validate-with-json-schema fails to XVRL report w/detections on invalid input

xml-project.com modified ticket #209

xml-project.com — Tue, 09 Sep 2025 13:27:35 -0000

p:validate-with-json-schema fails to XVRL report w/detections on invalid input

xml-project.com posted a comment on ticket #209

xml-project.com — Tue, 09 Sep 2025 13:27:35 -0000

Strange. If I run the pipeline, I get 2025-09-09T15:22:14.87+02:00