Hello,

Unfortunately this issue was not solved in Oxygen 22.1. It is scheduled to be solved with priority on the current version. Depending on the complexity we will add it also in an Oxygen 22.1 maintenance build. We will update this thread when will be fixed.

Best Regards,
Octavian

Hello Ruth,

We just released Oxygen XML Editor 22.1.
Please note that the issue that you reported was solved. Thanks for your feedback.

Best Regards,
Octavian

Hello Stefan, We just released version 22.1 of Oxygen XML Editor. Please note that the Oxygen Eclipse plugin now provides support to compare XML documents in the visual Author mode. https://www.oxygenxml.com/xml_editor/whats_new.html#22.1Visual_Comparison_for_Eclipse You can find more details in our...

Hello Ali,

I am not an XProc expert. Probably you can do this if you can pass the source as a parameter, and use the ${ask} editor variable in the parameter.

Best Regards,
Octavian

Hello Ali, Thanks for your feedback. Unfortunately we do not have support to provide the source as an ask editor variable. Only the transformation parameters can be passed as an ask editor variable. I added an issue on our issue tracker to add this support in a future version. We will update this th...

Hello, Thanks for your feedback. For JSON Schema validation, we automatically show warnings for each property that is not recognized in the current schema version. For the validation of a JSON instance with a JSON Schema, you need to add in the JSON Schema the "additionalProperties": false...

Hello, Thanks for your feedback. When a problem is reported on a text node the highlight will be added on the parent or on the previous element. We have an issue on our issue tracker to add a better support for locating text nodes. I added your comment on the issue and I increased its priority. When...

Hello, I don't understand all the usecase of your rule. Maybe it is easier if you check the number of uicontrol elements, something like this: <sch:pattern id="uicontrol-menuscascade"> <sch:rule id="uicontrol" context="uicontrol[not(ancestor::menucascade)]"> <sch:report...

Hello Bill, Yes, you can reuse the frameworks between the standalone versions of Oxygen and Web Author. We provide also Schematron with Quick Fixes support in Web Author. There is a topic in our user manual that explains how to create customized frameworks, how to test and upload your customization,...

Hello, You cannot reuse xs:alternative, you can reuse the types referred in the alternative. Here is an example: <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:vc="http://www.w3.org/2007/XMLSchema-v...

Hello, The problem is that the matches function allows only one node. If you specify "text()" as first argument, this means that all the text nodes from the current element will be matched. You have two options: 1. You can pass all the text content from the current element, by changing the...

Hello Ruth,

Thanks very much for your feedback.
I added an issue on our issue tarker to fix this problem in a future Oxygen release. We will update this thread when the issue will be solved.

Best Regards,
Octavian

Hello Riley, Thanks for your feedback. Yes, we should not expand automatically all transformation scenarios categories, we should preserve the collapse/expand state. I added an issue on our issue tracker to implement this in a future version. We will update this thread when it will be implemented. B...

Hello, Thanks for your feedback. Yes, this seems to be a problem. I added an issue on our issue tracker to analyze it and find a solution. We will update this thread when will be fixed. I reproduce this behaviour also with <oXygen/> XML Editor 21.1, build 2019090904. It seems that this happens becau...

Hello, Unfortunately I don't understand the problem from the examples that you send. Maybe you send us more complete examples. You can use this form: https://www.oxygenxml.com/techSupport.html Also, being an XSLT related question maybe is better to post it on the XSLT list "xsl-list@lists.mulbe...

Hello Martin,

We plan to have Saxon 10 as a plugin for Oxygen 22.1. I don't think we will provide the Saxon 10 plugin also for Oxygen 22.0.

Best Regards,
Octavian

Hello Rajneesh, I don't know what you do you mean by "always populated". If you want to make sure that a value is set for the alias1, coli1 and operator attributes, you can add a restriction on the string type. For example you can check that the length of the value is greater than one, som...

Hello Rajneesh, I think that you can add this constraint only using XSD 1.1 "xs:assert" or "xs:alternative", or maybe using a Schematron schema and create an assert there. You can read more about XSD 1.1 in the specification: https://www.w3.org/TR/xmlschema11-1/ Maybe you can add...

Hello,

I an not sure what you want to do. Maybe you want to declare a prefix for the schema, something like this: .

Best Regards,
Octavian

Hello, Thanks for your feedback. Unfortunately I cannot reproduce de problem. I tested with <oXygen/> XML Editor 22.0, build 2020021016, I created a new HTML file and pasted the content you provided, then run the XPath //p . The XPath result was returned correctly for the HTML5 document. Maybe you a...

Hello, I think that the "idref()" function will work only if you use Saxon-EE (schema-aware) for Schematron validation. For this you need to enable the "Use Saxon EE (schema aware) for xslt2/xslt3 query language binding" option from Options->Preferences dialog -> "XML / XML ...

Hello,

I think that the problem is that you compare the string values of the numbers. You need to convert the text value into a number using the number() function. The condition must be something like this "number($grossArea) >= $conditionedAreaValue".

Best Regards.
Octavian

Hello Grethel, Unfortunately, in Oxygen XML Editor version 18 the SQF "use-for-each" feature is not available. Therefore, you cannot use a quick fix that has the "use-for-each" attribute. The only way to avoid the error is to have this rule implemented differently for the two ver...

Hello,

As an update, the user tested and found that there is a problem on their side.

Best Regards,
Octavian

Hello Shabeer, You can define also a range of characters that are not allowed. You can have also a quick fix that will remove all not allowed characters from the document. I think in this case the Schematron must look something like this: <?xml version="1.0" encoding="UTF-8"?> <s...

Hello Shabeer, You can create a Schematron that will detect and show you an waning when a zero-length character is detected. You can also have some quick fix actions that will replace the character with space for example, or will delete the character. The Schematron can look something like this: <?x...

Hello Martin,

Thanks for your feedback.
Yes, it seems that the content compilation suggestion in this case is not correct, should not propose 'stylesheet-` and should propose `stylesheet-location` instead. I added an issue on our issue tracker to correct this problem.

Best Regards,
Octavian

Hello, You don't need a Saxon EE licence if you are transforming from Oxygen. It seems that there is a problem when you set the stremming mode from the configuration file.If you enable the stremming mode from the Saxon configuration dialog options, by checking "Enable streaming mode", and ...

Hello Stefan, There is a topic in our user manual that explains how to localize the Oxygen XML Editor Eclipse plugin. https://www.oxygenxml.com/doc/versions/21.1/ug-editorEclipse/topics/localizeGUI-eclipse-plugin.html But not all the keys are in "plugin_<locale>.properties". Please send us...

Hello Stefan, Yes, if you will use the Web Editor for DIFFs you will need another licence. If you are interested in this solution you can send an email on our support. The version 22.0 of the Oxygen XML Editor is scheduled to be released in February 2020, and version 22.1 probably few months later. ...