Hi, Contrary to the documentation ( XSLT Editor , XSLT Refactoring Actions , XSLT Refactoring ) on my machine the XSLT Refactoring Actions are only available when I start oXygen in "Developer" mode, not in "Editor" mode. I expected the "Editor" mode to be the full-fledg...

Many thanks for the update!

Frank

Thanks for the update!

Frank

Hi Radu,

Thanks for confirming my suspicion. At first I feared I had messed with my Author CSS

Frank

Just in addition to the above workaround because I think this is related: When choosing Show Profiling Attributes , the profiling attributes set on a table row are not shown, only the background color of the row changes and there is a colored frame around the row. I suppose this is the expected beha...

Thanks for the fix, Adrian.

Frank

Hi Adrian,

I've sent you the broken project file by e-mail.

Best regards,
Frank

Hi Adrian,

Thanks for the quick reply. The build number is 2016102619. I will send you the project file but I have to anonymize some customer data beforehand.

Best regards,
Frank

Hi, Trying to open an existing project file in oXygen 18.1 fails with the following error message. The project file looks okay so I suppose this might be a caching issue? I have been switching between oXygen 16.1 and 18.1 on the same machine. Any pointers welcome. Best regards, Frank java.io.IOExcep...

Hi Radu,

Thanks for the clarification. I suspected as much.

Kind regards,
Frank

Hi, I've created an "XML with XSLT" transformation scenario to preprocess DITA maps. The transformation scenario is stored on project level. Now I've noticed a strange behavior: Every time I open a DITA map in DITA Maps Manager the XSLT transformation scenario vanishes from the Transformat...

Hi Radu,

Many thanks for your quick reply and the workaround suggestions.

Best regards,
Frank

Hello, I'm using the ${ask} editor variable in an XSLT transformation to set a parameter value: ${ask('Product version', radio, ('A':'A';'B':'B'))} Is there a way to use this value not only as parameter for the XSLT script but also in the output file name of the transformation scenario itself (so th...

Just an update with some observations: Everything works as expected when using the standard DITA profiling attribute @audience . The problem seems to be related to our own specialized profiling attribute derived from @props , according to Eliot Kimber's Attribute Specialization Tutorial . I will inv...

Hi Radu,

I mean configuring the color scheme(s). I will have a look and report back. Thanks for the pointers.

Best regards,
Frank

Just a follow-up question: Is it possible to overwrite the highlighter files in DITA-OT/plugins/com.oxygenxml.highlight/highlighters/ from within our customization plugin? If not, that's no problem as we distribute the whole DITA framework and could configure the highlighters in the Highlight plugin...

Hi Radu,

It was just a matter of adding the following line to our plugins/com.parson.pdf2/Customization/fo/xsl/custom.xsl file:
Kind regards,
Frank

Hi Radu,

Thanks for the quick reply. I will have a closer look at our plugin and report back.

And yes, I've seen the licensing file in the plugin folder and will keep that in mind.

Best regards,
Frank

Hi, The syntax highlighting DITA-OT plugin " com.oxygenxml.highlight " works like a charm when using the standard PDF transformation. However, we are using a customization DITA-OT plugin on top of the "org.dita.pdf2" plugin: <require plugin="org.dita.pdf2"/> but the syn...

Hi Radu,

Your workaround does work. Many thanks for the pointer.

Best regards,
Frank

Hi Radu,

I've tried key scopes with this use case and they work like a charm. Unfortunately, we are still using DITA 1.2 with this customer.

Best regards,
Frank

Hi, When importing profiling attributes from a DITAVAL file oXygen creates an associated Profiling Condition Set that is bound to the DITAVAL file. In the Condition Set dialog, "Use DITAVAL File" is selected. However, when switching the Document type from "DITA*" to "My DITA...

Hi Radu, I've created a small sample project using standard DITA and everything works as expected. So the problem must be either with this specific project or with our custom oXygen framework. I will investigate further and report back. Best regards, Frank BTW I would have added the sample project t...

An additional observation. The order of the references to the key definitions and the subject scheme in the top map seem to matter:

Works: Subject scheme > Key definitions
Does not work: Key definitions > Subject scheme

Best regards,
Frank

I've found the culprit. We have defined a key that is identical with a subject definition. And as both are specialized from <topicref> they get in each other's way. So if you have the following subject scheme: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE subjectScheme PUBLIC ...

Hi Radu,

Thanks for looking into this. I will try with a stripped-down project and will also look for accidental unwanted references in the files.

Best regards,
Frank

Hi, I have a main map with two map references pointing to two different key definitions maps. <mapref href="user_key_definitions.ditamap" audience="users" processing-role="resource-only" /> <mapref href="support_key_definitions.ditamap" audience="support&...

Hi Radu,

Thanks for your kind help. I will try to create a project that exhibits this behavior and send it to your support address.

Best regards,
Frank

Hi, I'm using a subject scheme map to provide controlled values for a profiling attribute. However, I encounter a very strange behavior as some values are not picked up from the subject scheme map and are marked as invalid if used. In addition, I've also defined the values in oXygen's Profiling Sett...

Hi Radu,

Thanks for your reply. This is indeed a very special case and I will look into solving this problem with some post-processing.

Best regards,
Frank