Search found 14 matches
Search found 14 matches
• Page 1 of 1
- by dnl
- Fri Mar 26, 2021 7:03 pm
- Forum: Common Problems
- Topic: Possible bug in XPath option Find/Replace: using not()
- Replies: 3
- Views: 1260
Re: Possible bug in XPath option Find/Replace: using not()
Thanks for the clarification, Adrian. That makes sense. But perhaps you could make this more clear in the documentation and/or find/replace window what the context is. I find it somewhat irritating behaviour: * if you open Find/Replace and hit "Find", your context is the current cursor pos...
- by dnl
- Fri Mar 26, 2021 2:23 pm
- Forum: Common Problems
- Topic: Possible bug in XPath option Find/Replace: using not()
- Replies: 3
- Views: 1260
Possible bug in XPath option Find/Replace: using not()
I am puzzled by the following behaviour in Oxygen 23.0: * Find/Replace a string * Use XPath option: *[not(local-name() eq 'element_name')] -> It also shows matches in element_name (which is wrong). When I use the expression without not(), the predicate gets evaluated OK: * Find/Replace a string * Us...
- by dnl
- Thu Jan 07, 2021 3:19 pm
- Forum: Common Problems
- Topic: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
- Replies: 6
- Views: 2152
Re: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
Thank you Radu, I think many would approve such a scenario. Speaking for myself, most of the time in these transformations we do not even need EE capabilities.
- by dnl
- Wed Dec 30, 2020 11:53 am
- Forum: Common Problems
- Topic: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
- Replies: 6
- Views: 2152
Re: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
Thanks Radu, for the explanation. I didn't realize this might be a grey issue, because as far as I know you can only use this when running in Oxygen (even if it is an external call). However, perhaps you consider about including a default transformation scenario with Saxon PE or HE, since the curren...
- by dnl
- Tue Dec 29, 2020 7:51 pm
- Forum: Common Problems
- Topic: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
- Replies: 6
- Views: 2152
Missing the Ant with Saxon EE transformation scenario in Oxygen 23
Hi, I am missing the Ant scenario "ANT (with Saxon 9 EE XSLT support)". It is gone in Oxygen 23.0, build 2020111805. Without it, I cannot use XSLT 2.0 or 3.0 transformations by default. However, when I add the libraries manually like in the scenario "ANT (with Saxon 9 EE XSLT support)...
- by dnl
- Wed Jun 17, 2020 10:38 am
- Forum: Common Problems
- Topic: Schematron schema-aware attribute expansion
- Replies: 2
- Views: 1118
Re: Schematron schema-aware attribute expansion
Thank you Octavian for the explanation
- by dnl
- Tue Jun 16, 2020 7:23 pm
- Forum: Common Problems
- Topic: Schematron schema-aware attribute expansion
- Replies: 2
- Views: 1118
Schematron schema-aware attribute expansion
Hi, I fail to understand how the attribute expansion works in Oxygen. The XPath "element[@attribute]" in sch:rule/@context is always reporting even if the attribute is optional in the XSD and missing in the XML. Shouldn't the schematron fail to report since it is an optional attribute and ...
- by dnl
- Fri Feb 22, 2019 1:04 pm
- Forum: XQuery
- Topic: Saxon EE not available in Refactoring? Oxygen 19.1
- Replies: 1
- Views: 2574
Saxon EE not available in Refactoring? Oxygen 19.1
In an XQuery Update script, whenever I try to use an XPath 3.1 map expression, the script fails in XML Refactoring ("To use XPath 3.1 syntax, you must configure the XPath parser to handle it"). However, when I run the same XQU with a Transformation scenario on Saxon EE, it works without pr...
- by dnl
- Mon Sep 03, 2018 5:00 pm
- Forum: Feature Request
- Topic: XSD 1.1: elements view works poorly with xs:alternative
- Replies: 1
- Views: 2228
XSD 1.1: elements view works poorly with xs:alternative
While content completion runs smoothly, element view feels broken in some context. When there is an xs:alternative definition, the default behavior is: if there is no other element declaration of the same name (anywhere) in the schema, elements view does not offer anything. The test alternative is n...
- by dnl
- Wed Aug 29, 2018 3:10 pm
- Forum: XQuery
- Topic: Special entity & breaks in custom refactoring XQuery Update operation
- Replies: 5
- Views: 5214
Re: Special entity & breaks in custom refactoring XQuery Update operation
Thank you Radu, this works. Only issue there is with this workaround there is an error from Saxon in the transformation scenario: Programmname: Saxon-EE XQuery 9.7.0.19 Fehlerlevel: warning Beschreibung: net.sf.saxon.tree.linked.DocumentImpl@754b7981 Updated document discarded because it was not rea...
- by dnl
- Wed Aug 29, 2018 10:21 am
- Forum: XQuery
- Topic: Special entity & breaks in custom refactoring XQuery Update operation
- Replies: 5
- Views: 5214
Re: Special entity & breaks in custom refactoring XQuery Update operation
Thanks. I tried the script you named, it works without problems. Can you reproduce with the following script? Am I missing something in the serialisation options? Again, it works in the transformation scenario and only fails when called from the XML refactoring menu. Input: <?xml version="1.0&q...
- by dnl
- Wed Aug 29, 2018 9:48 am
- Forum: Other Issues
- Topic: Can I use Oxygen variables with custom refactoring descriptor file?
- Replies: 4
- Views: 2560
Re: Can I use Oxygen variables with custom refactoring descriptor file?
Thanks, this would be a great enhancement. As a workaround I will use document-uri(), but I wanted to avoid having to use function chaining like replace(document-uri(),tokenize(document-uri(),'/')[last()],'') (is there a simpler way for saying "give me the path of the current file"?) Thanks!
- by dnl
- Tue Aug 28, 2018 6:08 pm
- Forum: Other Issues
- Topic: Can I use Oxygen variables with custom refactoring descriptor file?
- Replies: 4
- Views: 2560
Can I use Oxygen variables with custom refactoring descriptor file?
https://www.oxygenxml.com/doc/versions/ ... iptor.html
I want to make the path of the current XML file available to the XQuery update script in my custom refactoring operation.
Is it possible to pass ${cfdu} in the descriptor file?
I want to make the path of the current XML file available to the XQuery update script in my custom refactoring operation.
Is it possible to pass ${cfdu} in the descriptor file?
- by dnl
- Tue Aug 28, 2018 4:04 pm
- Forum: XQuery
- Topic: Special entity & breaks in custom refactoring XQuery Update operation
- Replies: 5
- Views: 5214
Special entity & breaks in custom refactoring XQuery Update operation
My XML file contains two predefined XML entities: """ and "&". I am confused by the following behaviour: * when I run my XQU script using a transformation scenario, the entities are untouched (= everything is OK) * when I run my XQU script using a custom refactoring oper...
Search found 14 matches
• Page 1 of 1
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service