Hi Cristian,

indeed this worked for me.

Thanks a lot.
Patrik

Hi, with css I have this rule: service > *:before { width : 22em; content : " " name() ": "; } service > * { display : block; content : oxy_textfield(edit, "#text", width, 30em); visibility : -oxy-collapse-text; } The idea is to have vertially alligned text fields with the element name in front of i...

Hi, we have a central XML file for which we need a comfortable way to edit it - preferably from anywhere within our intranet. If I would edit the file locally with oXygen XML editor I would create a custom framework including identification of file type by file name or content XSD file schematron fi...

Hi, I have created the following simplified test case: <root> <element1> <child/> </element1> <element2/> </root> <sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"> <sch:pattern> <sch:rule context="root"> <sch:assert test="false()" subject="element2">Test1</sch:assert...

Hi Alex, I just found out that oXygen 20.0 includes Saxon 9.8.0.8 which supports XSLT 3.0 in HE. So I will try to switch to the new version tomorrow. (And adding some more parameters like generate-id() to the output also works good as a workaround or now.) Thus, there's no need for an additional plu...

Hi, with oXygen 18.1 I configured SaxonHE-9.8.0.10 as custom transformer. And within my xslt I use xsl:message to write some debugging information. It seems that oXygen filters the messages to remove duplicated lines. So for instance with this template <xsl:template match="/"> <xsl:for-each select="...

This one works fine. Thanks, Radu! :)

Patrik

Hi, I want to use the latest Saxon-HE version (9.8.0.8) with oXygen using my own configuration file that registers extension functions. Thus, I also need to use an additional library that implements these functions. I already managed to configure SaxonHE-9.8.0.8 as a custom XSLT engine but I can't g...

Great, thanks Radu.

Hi, I have added several annotations to my (generated) XSD to help the author when editing the XML in text mode. Is there any other way to display the annotation beside the tooltip that appears when hovering with the mouse and wait a little? My issues with this behavior are: You have to use the mous...

Thanks Adrian, this solution works fine with me.
Regards,
Patrik

Hi, I have multiple XSD with embedded schematron rules. When validating an xXML file referencing one of the XSDs the embedded schematron rules are not checked. I knkow I can create a validation scenario but I have to set a specific XSD to enable the "Embedded Schematron rules" check box. But then I ...

Hi, I just learned about the existence of xslt documentation (by elements in the namespace "http://www.oxygenxml.com/ns/doc/xsl"). I'm not interested in generating a seperate documentation for my code but it would be great if the description of the variables, functions, templates and parameters woul...

Hi,

just as a reminder (I already discussed this with Alex): It would be nice to have an XML Refactoring option that allows you to enter an XQuery Update statement or alternativly to refer to an XQuery Update script.

Regards,
Patrik

Just in case anybody else has this problem: I found a nice way to handle custom extension functions: Just declare them in your xslt like this: <xsl:function name="my:myCustomFunction" as="xs:string" use-when="not(function-available('my:myCustomFunction'))"> <xsl:param name="1stParameter" as="xs:stri...

Hi, this is more a vague idea than a request, but it might be usefull... While the template pattern mechanism of XSLT is very comfortable to extend it has the same deficit as CSS has: On large projects it is difficult to maintain the overview which template will match (first) on a specific node. For...

Hi Radu, I agree, that for standard tables (e.g. in DITA) the placeholder is better to be hidden - especially when you have plenty of emptyy cells. But when using custom XML (or specialized DITA) the placeholder is very useful - especially when you have a schematron rule complaining about empty elem...

Hi, In all my empty table cells there is no placeholder displayed - even when I explicitly set -oxy-show-placeholder:always; by css. I know I could define a css rule to manually display some content for empty elements. But I'mstill wondering why this seems not to work by default as it does for other...

Hi Radu,

Thanks, I would support both ideas. (Although the realization will be too late for my current experiments).

Regards,
Patrik

Hi, currently I'm experimenting a lot with different schematron checks an tweaks for the execution of the checks. So it would be very helpful to measure the execution time of the validation ('DITA Map completeness check' for Map Manager) for comparision. Is there any better way then manually waiting...

Sounds good. Thanks.

Hi, it would be helpful if the settings for "DITA Map Completeness Check" from the DITA Map Manager would be stored in the project file - just like it can be done for ordinary validation and transformation scenarios. I know I can export and load the settings but it's still not very comfortable when ...

Ok, Thanks.

Patrik

Hi, I have some projects with a growing number of transformation scenarios. So it's becoming uncomfortable to find the right one. Maybe some kind of folder mechanism would be nice so you can organize them. This might also enable you to easily select a set of transformation scenarios - e.g. for publi...

FYI: I just updated my DITA-OT-Plugin https://github.com/dita-semia/org.dita-semia.topic-num to handle equations as well. So it will add consecutive numbers to their title and to the cross reference.

Patrik

You would have needed the :nth-child() only when your entry element were identical (e.g. entry, entry, ... instead of entry1, entry2, ...).

Patrik

You can do this nicely with existing css (I think supported since oXygen ~v17.1): my-table > my-row:first-child > *:before { // set styling for all header cells display: block; background-color: gray; // imitate table header font-weight: bold; border-bottom: solid 1px black; // imitate seperate row ...

Hi, I have an xsd-based DITA map and a schematron file with rules evaluating the class attribute. So, obviously, the default attributes need to be expanded before validation. To validate a single topic I have to enable the option "Use Saxon EE (schema aware) ...". Otherwise my rules don't hit anythi...

Thanks for the explanation. But I did not mean the automatic validation (although I might add it there as well) but the "Validate and Check for Completeness" in the DITA Maps Manager.

Regards,
Patrik

Thanks. It's not that urgent anyway since the current behavior is good enough...

Regards,
Patrik