It is not a requirement of oXygen, it is an XML requirement. You cannot enter < and & directly in a text, you need to XML escape that. You can use a CDATA section and inside that you can enter < and & without escaping. So for example instead of <codeblock>Sample text containing < and &</...

Thanks! To fix this please go to Options->Preferences -- Editor / Pages / Author -- Format and Indent, and select "The entire document" instead of "Only the modified content". It seems the partial serialization done when the Author tries to change only the actually modified contr...

Hi,

The xpath-default-namespace value is inherited from the closer ancestor that defines it. So, just add xpath-default-namespace="" on the templates that match content from the document from no namespace to reset the XPath default namespace to no namespace.

Best Regards,
George

Hi, I tried to reproduce a similar behavior but I was not able to do that. It will be great if you can identify a document, a set of operations and the wrong result and send that either to support at oxygenxml.com or post thhem directly on the forum if you manage to get small samples. Sure, elements...

Is there anyway to obtain a log of the settings or subsets of the settings? I am sorry, what settings are you referring to? I see that I did not answer to one of the previous questions. Many oXygen options can be stored inside the project .xpr file if you set the "Project Options" option ...

Your document is not XML wellformed. You cannot write < directly in XML, you need to escape it as < FWIW here it is an example tested schema: <?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3....

Please post a sample XML file that we can use to reproduce the problem. You can cut parts from your file until you get to a minimum that still shows the issue.

Best Regards,
George

You can reset the default namespace only on an ancestor element. In your case that is the root element and you mentioned that you want to specify that with no prefix so it is not possible to have the default namespace for root and also the xmlns="" for the children.

Best Regards,
George

Hi Stefan, Learning Schematron is a good investment and it is very easy to learn. There are available also a few tutorials, check the ones from Roger Costello and Dave Pawson. However, as you probably know oXygen includes Saxon Enterprise Edition and that offers along with the XSLT 2.0 and XQuery pr...

To make this work you need to add in schema_a.xsd <xsd:import namespace="http://b"/> and make sure you enable the "Process namespaces through uri mappings for XML Schema" in Options->Preferences -- XML / XML Catalog in oXygen standalone. In Eclipse the location is Eclipse->Prefer...

AKAIK the work is in progress, although indeed it is not easy to find the schedule. The current status is "Last Call Working Draft": http://www.w3.org/TR/xmlschema11-1/ *** This W3C Last Call Working Draft specifies the W3C XML Schema Definition Language (XSD) 1.1. It is here made availabl...

Your samples have a few errors. However, after correcting those in the second sample I got it working without issues: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" exclude-result-prefixes=...

You can use the Saxon collection function to access all documents from a folder. Then, the XSLT transformation to get the text inside Texte is simple, just match on that element and output its value with something like <xsl:value-of select="."/> The further analysis that you need for the t...

Hi John,

The NVDL script can attach all the XForms sections if you take also the initial XHTML section in that validation candidate. That means that you need a schema that accepts the initial XHTML section and the XForms content.

Best Regards,
George

Hi John, I corrected an issue in Jing - it did not check ID/IDREF constrains from XML Schema validation, see http://code.google.com/p/jing-trang/issues/detail?id=114 and the XForms NVDL script splits each XForms section in a separate validation candidate, that is there are multiple validate operatio...

Hi David,

No problem, thanks for the follow up. This will be a useful topic for people searching our forum for a similar issue.

Best Regards,
George

There are two possibilities, depending on the XInclude processing. If XInclude processing is enabled then the parser will replace the XInclude elements with the actual included content before the Relax NG validation so your Relax NG schema does not need to declare the XInclude elements. If XInclude ...

Please see also the follow-up topic
http://www.oxygenxml.com/forum/topic5211.html

That is expected to be available in a few weeks, end of August/beginning of September.

Best Regards,
George

Hi,

Please vote for the splash screen for oXygen version 12:
Variant 1


Variant 2


Variant 3

Hi Paul, Thanks again for reporting this issue. I logged an bug against Calabash as it reports the XSLT engine warnings as errors. We were able to find a workaround for this and that will be available in the next oXygen release. For more details please see http://code.google.com/p/xmlcalabash/issues...

Hi Paul, We were able to obtain the same error in oXygen by adding a line like below in the personal.xsl from oXygen samples and then running the xproc/transform.xpl pipeline: <xsl:value-of select="namespace::*/preceding-sibling::*"/> We will look into this and let you know as soon as we h...

Hi Paul,

In [oxygen]/lib/xproc/calabash/engine.xml look for the engine/@engineVersion attribute. The latest version should have engineVersion="0.9.23".

Best Regards,
George

Hi Paul,

I uploaded initially the latest calabash integration in a wrong location the URL I posted to the xproc-dev list pointing to the previous integration. Please make sure you have the latest one and let us know if you see the same issue.

Best Regards,
George

You can define that as a choice of a followed by the other optional elements (b, c, d, etc.) b followed by the other optional elements (c, d, etc.) c followed by the other optional elements (d, etc.) etc. If you have 4 elements then in DTD like notation that will be (a, b?, c?, d?) | (b, c?, d?) | (...

Hi Paul,

Thanks for updating the post, I am happy to hear the issue is solved with the new Calabash and the new connector.

I was about to post also here the link to the updated Calabash connector
http://www.oxygenxml.com/update/calabash-oXygen.zip

Best Regards,
George

Hi Paul,

We will make available this afternoon a connector for the latest Calabash (the one released a few hours ago). I will post the link also here as soon as it will be available. Then please try the same pipeline with that and let us know if you still get this problem.

Best Regards,
George

oXygen introduced some time ago the concept of validation scenarios, similar with the transformation scenarios. This allows to specify multiple validate actions to be performed as part of the validate command and more, these scenarios can be easily associated with a set of files from the contextual ...

Hi Patrick,

Please note that XInclude elements are replaced before the validation so the schema needs to refer to the elements replacing the XInclude elements, that is in your sample foo should allow bar as its child element.

Best Regards,
George

Dear Patrick, oXygen has support for this. Please look at validation scenarios: http://www.oxygenxml.com/doc/ug-oxygen/validation-scenario.html You need to define a validation scenario for your sub.xml module and set the main.xml file as the file to be validated. Thus sub.xml will be validated indir...