Hi, i just changed to oxygen 15.2 and got now errors within my xsd-embedded schemtron rules: [Schematron 1.5] cvc-complex-type.4: Attribute 'name' must appear on element 'sch:pattern' [Schematron 1.5] cvc-complex-type.2.4.a: Invalid content was found starting with element '{"http://www.ascc.net...

Hi Alex,

thanks alot - it worked on the first try. :)

Regards,

Patrik

Hi, I want to apply an XSLTOperation on the root element replacing the previous one. I don't get any error messages but the content is not being replaced. I guess there is a special behavior required in TransformOperation for the case that the root node needs to be replaced instead of the following ...

Hi Sorin, finally I'm back to this topic... Thanks for your replay, but we found no easy way to formulate suitable hyphenation patterns. However, we found another solution that works fine for us so far (in case, someone else has this problem): In the transformation for the fop-generation we add an a...

Hi, since one use-case of oxygen is writing specifications in a dita-derived document-type we have lots of identifiers in our texts. For these the standrd hyphenation patterns are not sufficient. For instance identifieres like THIS_IS_AN_IDENTIFIER or ThisIsAnIdentifier. Suitable hyphenatin points w...

Thanks alot to both of you. Since I want to avoid having to copy (and maintain) the original attributes in the new definition I sticked to redefine according your desctiption and it works - without warning! :-) (Still good to know about the override element - will surely use it soon.) Regards, Patrik

Hi, I have two document types: 1. for generic documents (a specialization of dita) 2. for specifications In the first one for instance the topic and section elements (and several others) have the attribute audience. I realizes this by deriving these types from a common base type containing these att...

Hi, in my dita-derived docmuent type I'd like to ake the attributes @audience, @product and others visible and editable with oxy_popup (provided they are already set). Now in several cases the suitable place for these markers is not right before or after the element but after the first child element...

Hi Radu,

the idea with my own extension function for saxon I also already tried but failed to get it working. However, now I discovered the existing extension function saxon:transform which does just what I was looking for...

Thanks

Patrik

Hi, I extended the dita conref to an XsltConref which adds an xslt transformation to the referred content before displaying it. In the author view I implemented my own ReferenceResolver and it works fine. Now I want to generate a pdf with fop from my document so I have to resolve the XsltConref with...