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

Hi Radu, Thanks for looking into this. I use <xref keyref="Cmd.SelectFile"/> . This displays a link with the value of the <keyword> in the PDF output. However, because the linked topic from the key definition is not included in the short document version's DITA map the link doesn't work bu...

Hi Radu, Many thanks for your quick reply. The Validate and Check for Completeness function already can "Report links to topics not referenced in DITA Maps". Admittedly, doing a similar check for keyref-ed topics in a map is a bit tricky but would be a useful enhancement. Best regards, Frank

Hi, I'm using the Export DITA Map function to export only a short version of a longer document (oXygen 16.1). I use keyrefs like the following one: <keydef keys="Cmd.SelectFile" href="../topics/cmd_Select.dita"> <topicmeta> <keywords> <keyword>Cmd.Select</keyword> </keywords> </t...

Thanks for the follow-up, Radu! This is a great feature which a lot of customers request.

Kind regards,
Frank

Hi Florin,

Many thanks for your thorough reply! I will test your suggestions as soon as possible. However, as this is production data I don't want to do too much testing so this may take some time.

Kind regards,
Frank

Hi, I'm using the Syncro SVN Client of oXygen 16.1. Strangely, even after updating the repository all svn:externals show as "outgoing changes". TortoiseSVN on the other hand shows them correctly as "unchanged". Can this be some misconfiguration on my side? Kind regards, Frank

JFTR, see also "WebHelp: Chunking breaks CSS paths" where the problem was caused by an old DITA-OT version (1.8.4?).

Frank

I finally got around to look at this issue again while solving "WebHelp: Chunking breaks CSS paths" . I noticed that the com.oxygenxml.webhelp plugin and other, dependent ones in our framework differed substantially from the original ones. Looks like we branched the framework off of an old...

Hi Bogdan, Thanks to your pointer I found the culprit. When comparing our customized common.xsl with com.oxygenxml.webhelp/xsl/dita/desktop/common.xsl I noticed that the com.oxygenxml.webhelp plugin and other, dependent ones in our framework differed substantially from the original ones. Looks like ...

Thanks, Radu!

Sorry for the late reply. Bogdan's instructions worked like a charm. I use the webhelp.head.script parameter in the transformation scenario to add my custom JavaScript to every HTML page in the output. The path is given as an URL: file:/path/to/my/custom_webhelp_javascript.html . No modifications to...

Hi Radu, Thanks for your quick reply. That link on my profile page is indeed there: https://www.oxygenxml.com/forum/search.php?author_id=26644&sr=posts However, the layout is different and the link reports every single post , whereas the old link (https://www.oxygenxml.com/forum/search.php?searc...

For the record, here's Bogdan's reply to my mail: Hello, I saw that your transformation uses a custom DITA-OT and probably a customization of the standard WebHelp plugin. You should check your XSL customizations. In the standard DITA WebHelp transformation the CSS and JS paths are generated by the &...

Hi,

I'm missing the old and very convenient "View your posts" link in the forum. Fortunately, my old bookmark is still working: search.php?search_id=egosearch

Best regards,
Frank

Hi George,

Thanks for the clarification.

Kind regards,
Frank

I've just created a report from the same DITA map with the oXygen 16.1 and oXygen 17.1 versions of the report script. I don't quite understand the results because the oXygen 17 version reports more reused elements (because of the @conkeyref'ed elements) and words but a lover reuse percentage. How ca...

EDIT:

The above code resides in Oxygen XML Editor 17\frameworks\dita\report\modules\resolve.xsl

Frank

It's there in oXygen 17.1, in Oxygen XML Editor 17\frameworks\dita\report\ report.xsl <!-- CONKEYREFs --> <xsl:template match="*[@conkeyref]" mode="resolve-base resolve"> <xsl:param name="keyspace" tunnel="yes"/> <xsl:variable name="key" select="...

Hi George,

Thanks for this information. Our client is still on oXygen 16.1 but I will have a look in oXygen 17 or 18.

Kind regards,
Frank

Hi George,

Is this feature already implemented in oXygen 16?

Best regards,
Frank

Hi Alex,

Sorry for the late reply. Many thanks for your suggestions. I will try them and report back.

Best regards,
Frank