Hi Radu,

Many thanks for this information.

Kind regards,
Frank

Hi Radu,

Many thanks for the pointer!

Best regards,
Frank

Hi, I like the idea of creating a custom framework extension for sharing instead of copying a whole framework. What I don't understand yet is how the connection to the base framework is kept. I suppose it's settings like the following in the .framework file: <field name="extendedPersistentObjec...

Hi,

When using Oxygen 21.1 for the first time I got asked whether Oxygen can fetch validation schemas from remote URLs. I have agreed to trust all sources but now want to change this because I'm using Oxygen in a restricted environment with no internet access. How can I do this?

Best regards,
Frank

Hi Alin,

Many thanks for this extensive explanation and the example!

Best regards,
Frank

Found this related issue in the DITA-OT tracker with some hints how to solve my problem: Bug in "dita-utilities.xsl" getVariable when called from string context https://github.com/dita-ot/dita-ot/issues/2512 From any context, I think this would provide a mechanism to override the language,...

Hello, I have created a customization of the Oxygen WebHelp. One of the XSLT templates matches <xsl:template match="toc:topic> . Inside this template I use <xsl:call-template name="getVariable"> for some localized text. The problem is that somehow no language values seems to be availa...

Hi Anton,

The usual way in XML is to use one or both of the following entities:

Carriage return: &#xD;
Line feed: &#xA;

I haven't tested this, though.

Best regards,
Frank

Hi Radu,

Sorry for the late reply. I will have another look and try your suggestion.

Best regards,
Frank

Hi Radu, I'm trying to add a parameter to my custom PDF Review plugin . build_reviews.xml I've added the following line to build_reviews.xml : <param name="ct.change-bar.color" expression="$(ct.change-bar.color)" if="ct.change-bar.color" /> The value of the parameter ge...

Many thanks for this information.

Best regards,
Frank

Hi,

I have an additional question:

Is the footer text "Generated by <oXygen/> XML WebHelp" required when our customer publishes their customized WebHelp on their website? Or can they change the text?

Best regards,
Frank

Here's an example for the syntax, taken from com.oxygenxml.webhelp.responsive/oxygen-webhelp/page-templates/wt_search.html : <whc:macro value="${i18n(jump.to.results)}" /> The string is defined in com.oxygenxml.webhelp.responsive\oxygen-webhelp\resources\localization\strings-en-us.xml : <s...

Hi Ionela,

Many thanks for this information.

Best regards,
Frank

Many thanks for the pointer, Anton. That's indeed the more elegant solution.

Best regards,
Frank

Hi, As a CSS workaround, you could try changing .wh_footer { position: relative; } to .wh_footer { position: fixed; } . That would make the footer stick to the bottom of the browser window. However, I haven't done any thorough testing so this fix might have undesired side-effects. Best regards, Frank

Hi Radu,

Many thanks for your reply. Making the whc:webhelp_publication_toc component available for other pages would be appreciated.

We will consider your suggested workaround and get back to you if necessary.

Kind regards,
Frank

Hi, I'm customizing the WebHelp Responsive and want to insert an HTML fragment that contains text that must be localized. I've read "How to Localize the Interface of WebHelp Responsive Output" and suppose that I must add my string to one of the translation files and then reference it in th...

Hi Costin, My thumbs-up as well for such a feature because our customer wants the complete publication TOC to show on all pages (index, topic, search). I've tried copying the <whc:webhelp_publication_toc> section from the wt_topic.html template to the wt_index.html template. The container <nav> elem...

Hi Radu,

Many thanks for the update. We have already fixed some additional minor issues ourselves but knowing that the 1.8.x/2.x branch is now up-to-date is a big help!

Best regards,
Frank

Hi Radu, We took the plugin the DITA-OT_1.8_2.x_compatible branch and integrated it into Oxygen 20.1. However, we got an error message and noticed that the file review-pis-to-elements-pdf-classic.xsl was missing in that branch . We copied it over from the master branch at the plugin now works as exp...

Hi Radu,

Many thanks for your quick reply. We have forked the repo and will probably create our own plugin as a first step. If anything useful comes out of it we will contribute back to the community

Best regards,
Frank

Hi Radu, We want to modify the way review changes are displayed in the PDF output (change bars instead of foot notes). However, we haven't figured out the best way to do this. Is there any extension point? Or can/shall we just override the XSLT in the com.oxygenxml.pdf.review plugin? If we could mak...

Hi, We finally managed to extract version-related metadata from maps and topics by overriding com.oxygenxml.webhelp/xsl/ macroExpander.xsl and defining the following variable: <xsl:variable name="ProductVersion"> <xsl:choose> <xsl:when test="//topicmeta/metadata/prodinfo/vrmlist/vrm&q...

Hi Radu,

That's great! Many thanks for fixing this.

Best regards,
Frank

Hi Radu,

Many thanks for this pointer. Our customer still uses oXygen 17.1 but I will try your suggestion and report back.

Best regards,
Frank

Hi, We deploy an oXygen DITA framework that uses a custom DITA-OT plugin that comes with a .jar library. I know how to add libraries to transformation scenarios but that would require all users to update or re-create their existing transformation scenarios. Is there another way to add and deploy a ....

Just an update regarding the DITAVAL import:

Recent versions of oXygen add *DITA* (with two wildcards) as document type when importing DITAVAL files so above mentioned issue with a document type of "Customer DITA" is solved.

Best regards,
Frank

Hi Alin, The macro mechanism helped indeed with another issue; thanks again. What I want to do is creating release notes in WebHelp output, similar as https://github.com/doctales/org.doctales.release-notes does for PDF output. However, using the following XSLT variable on the top document level is e...

Hi Alin,

Many thanks for this pointer. I wasn't aware of this mechanism. I will give it a try and report back.

Best regards,
Frank