Norm Tovey-Walsh
- Login: norm
- Introduction email sent: Yes
- Which product do you use?: Saxon
- Registered on: 2020-08-27
- Last connection: 2023-03-29
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 3 | 59 | 62 |
Reported issues | 13 | 50 | 63 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
Non-Conformances | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
Saxon-CE | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
SaxonC | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
SaxonJS | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
SaxonMirrorHE | Manager, Developer | 2020-11-23 |
W3C QT Specifications | Manager, Developer, Reporter, Subscriber | 2020-08-27 |
Activity
2023-03-30
-
> What kind of "parsing" in Python do you use to pass HTML (as an PyXdmNode?) to SaxonC? Or are
> you parsing the HTML into XHTML?
I’m using the HTML parser to get an XML serialization which I then
reparse. It’s ugly, but ... Saxon/C Help and Discussions: RE: SaxonC 12.1 EE Query.exe on Windows: how to use XPath 4.0 function parse-htmlWith Saxon EE 12.1 Java, it seems to have support for the XPath 4.0 (proposed) `parse-html` function I need to put e.g. `htmlparser-1.4.16.jar` on the Java classpath.
What about SaxonC EE 12.1 where I can't put anything on the classpa... -
> Any answer here on how to use SaxonC EE and fn:parse-html?
Extensibility is an interesting challenge in SaxonC. I don’t know what
the right approach is, longer ...
2023-03-24
-
I've published XML Resolver 5.1.2 that removes the dependency on xml-apis. I've updated the builds for Saxon 11.x, 12.x, and trunk to use it, and exclude xml-apis for good measure. Bug #5931 (Resolved): Please do not include outdated xml-apis in the Maven consumable artifactThe Maven artifact [net.sf.saxon:Saxon-HE](https://central.sonatype.com/artifact/net.sf.saxon/Saxon-HE/12.0/overview) depends on xml-apis:xml-apis (brought by the transitive dependencies mechanism through [org.xmlresolver:org.xmlresolver...
-
... -
Added code to check for `file:` URIs in output files. They're unwrapped to just paths, being careful on Windows to remove the leading slash before a drive letter. Bug #5940 (Resolved): Should we resolve implicit (or explicit) file: URIs for the -o option?The documentation is clear that `-o` is a filename, but...
1. If a user specifies `-u`, it's very tempting to specify a `file:` URI for `-o`
2. Even if a user *doesn't* specify `-u`, we detect `file:` URIs on inputs implicitly, shoul... -
1. If a user specifies `-u`, it's very tempting to specify a `file:` URI for `-o`
2. Even if a user *doesn't* specify `-u`, we detect `file:` URIs on inputs implicitly, shoul... -
Fixed by making sure we call a `DirectResoureResolver` as well as the catalog resolver. Bug #5939 (Resolved): Using -u and a file: URI as the source argument for a query doesn't workActually, any URI that isn't resolved through the catalog will fail.
-
2023-03-23
-
This appears to have been caused by an unpinned reference to the `delvewheel` process which was upgraded after our last release. The new versions attempt to deal with delayed loading of DLLs by adding this '.pth' file but that clearly br... Bug #5934 (Resolved): SaxonC Python wheels don't work in a virtual environment on WindowsIssue Reported by user here: https://saxonica.plan.io/boards/4/topics/9334
I get a strange error (probably on the console error output) running any Python using saxonche 12.1 from PyPi in a venv environment under Windows:
```
C:\U... -
https://github.com/pypa/cibuildwheel/discussions/1440
And possibly related:
https://github.com/python/cpython/issues/78125
Also available in: Atom