Patrick Gundlach
Patrick Gundlach
(Sorry for spamming you). I assume that the error also happens when you use 4.16 and `sp --xpath lxpath`?
There are currently no difference in the layout or xpath functions. The XPath expressions can now access parent nodes (`../`) and you can use predicates in square brackets (`element[ ....
Version 4.17.5 has a new option (still experimental, undocumented): sp --option xmlfile=true or in `publisher.cfg` xmlfile=true Which writes the internal representation of the XML data to intermediate files and skips...
(now online at https://download.speedata.de)
This looks much better. But unfortunately impossible to track down without layout or data. If you think you can send a copy.. The contact data is at https://www.speedata.de/imprint/
Still hard to debug. lxpath is more strict than the old parser but there can be errors of course. I feel your pain but currently I cannot do very much.
I think you should stay with the luxor xpath parser, it won't go away. Just set it to default in your project. For new projects I'd recommend keeping the new...
Just in case you are still interested: the version 4.17.10 has a new implementation of the lxpath parser which should use much less memory while parsing XML files. Since I...
This issue is okay.
I can reproduce the problem, thank you very much for the report. I am not sure how fast I can fix it, but I give my very best...