Siebe Jongebloed

Results 6 issues of Siebe Jongebloed

i18next::backendConnector: loading namespace translation for language nl-NL failed failed loading /static/langs/nl-NL.json; status code: 404

:lady_beetle: **Describe the bug** Viewing the web-page this is the message in my console: `i18next::backendConnector: loading namespace translation for language nl-NL failed failed loading /static/langs/nl-NL.json; status code: 404` :computer: **Components...

🪲 bug

writing a node to a zip:inline-entry removes comment()-nodes inside the node

Add attribute @value to a pipeline:parameter

Instead of a element `` inside `` it would be nice to just use a attribute `@value` It would look like ``` ```

Using resp:response to download xml transfers name-space declarations

Using resp:response to download xml transfers name-space declarations. input-xml: see input.xml in input.xml.zip [input.xml.zip](https://github.com/Armatiek/xslweb/files/10012416/input.xml.zip) request-dispatcher.xsl template ``` ``` issueMetNamespaces.xsl: ``` application/xml attachment; filename=output-response.xml ``` The result of saxon-result-document: [output-saxon.xml.zip](https://github.com/Armatiek/xslweb/files/10012566/output-saxon.xml.zip) The...

cdata-section-elements attribute in xsl:output does not seem to be respected in pipeline-step

1 comment

I have declared a cdata-section-elements attribute and also declared output:serialization-parameters. When I use this in stand-alone transformation using saxon-he 10.5 (i.e. using XML Developer), the elements mentioned in the cdata-section-elements...

Creating a pipeline step with just a call to a external command

If I want to call to an external command after a pipeline-step, it seems now only possible inside a xslt. It would be nice if there could be a pipeline-step...