Issue with file paths to specific resources

[Bas10R]

Hello,

I'm using Oxygen XML Editor version 26.0 and I've encountered a minor issue with the WebHelp Responsive transformation scenario.
In the HTML output, references to specific resources result in mixed paths (with both forward and backward slashes), which come up as broken links in my CI's HTML checker.

Examples of the elements that produce broken links in the output:

Code: Select all

<link rel="shortcut icon" href="../../oxygen-webhelp\template\resources/images/favicon.png"/><link rel="icon" href="../../oxygen-webhelp\template\resources/images/favicon.png"/>

Code: Select all

<img src="../../oxygen-webhelp\template\resources/images/logo.svg" alt="Back to home page"/>

Interestingly, the only broken links are to the resources that I referenced in my publishing template:

Code: Select all

<resources>
            <!-- Main CSS file -->
            <css file="styles.css"/>
            <!-- CSS for notes -->
            <css file="notes.css"/>
            <!--Logo-->
            <logo 
                file="resources/images/logo.svg" 
                alt="Back to home page"/>
            <!--  Favicon -->
            <favicon file="resources/images/favicon.png"/>
            <!--Custom JS-->
            <fileset>
                <include name="js/custom-collapsed-sections.js"/>
            </fileset>
            <!-- Images -->
            <fileset>
                <include name="resources/**/*"/>
                <exclude name="resources/**/*.svn"/>
                <exclude name="resources/**/*.git"/>
            </fileset>
  </resources>

Kind regards,
Konrad

[Costin]

Hi Konrad,

Thank you for the feedback you provided!

We are aware of this issue and we have it already logged in our internal tracking system.
Therefore, I've just added your feedback to it and tried to prioritize it.
We will notify you by replying back on this thread whenever a fix will be implemented (in a future version of the software).

Regards,
Costin

[Bas10R]

Hi Costin,

Thank you for your reply.
Is there any workaround in place for this?

Kind regards,
Konrad

[cosmin_andrei]

Hello,
Unfortunately, there are no available workarounds.