Page 1 of 1

Transformation Output File Paths are platform-specific

Posted: Fri Mar 29, 2019 5:56 pm
by sarcanon

Using OxygenXML 21.0, I move frequently back and forth between Windows on my desktop and Mac OS on my laptop. One annoying problem I cannot figure out how to get around is that Oxygen appears to save output file paths in XSLT transformation scenarios in a platform-specific manner.

For instance, assume I specify a relative output path (Save as) on Windows, e.g., ${pd}\..\output\exports\foo.xml. I then move to my laptop and open the same project file, the path retains the Windows directory delimiters, storing the result file using the Windows delimiters, and thus with the wrong name and in a path not intended.

So, my question is, is it possible for Oxygen XML to automatically translate the directory delimiters in a platform-aware manner, so that the output file ends up in the correct location?

Thank you.

Re: Transformation Output File Paths are platform-specific

Posted: Mon Apr 01, 2019 12:46 pm
by Radu

When specifying output paths you should always use "/" as it works both on Windows and Mac/Linux. So specify the paths something like:

Code: Select all

and the scenario should work as well on Mac as it does on Windows.
I will add an internal issue on our side to automatically save the path with the proper separators so that the project scenarios can be used on any platform.


Re: Transformation Output File Paths are platform-specific

Posted: Thu Oct 17, 2019 3:16 am
by csquires
I'm having the same issue with the responsive webhelp output on Linux, and my output is set to ${cfd}/temp/${cfn} (my publish template location is set to ${pd}/publish_template/lgc/lgcblack). Since I generate the output on Windows but our end users are on both Linux and Windows. On linux the logo in the header does not show up because the path it points to is

Code: Select all


All other links to items in my publishing template use the generic path except for the path to the logo and favicon. For example my opt file has:

Code: Select all

            <css file="master.css"/>
            <css file="lgc_black.css"/>
            <css file="lgc_topic.css"/>
            <logo file="LEFT_RGB.png"/>
            <favicon file="img/halicon.png"/>
                <include name="img/**/*"/>
                <exclude name="img/**/.svn"/>
                <exclude name="img/**/.git"/>
The style sheets in the output head show up correctly:

Code: Select all

but the logo and favicon do not:

Code: Select all

Is there a way I can fix this so the paths for the logo is correct?


Re: Transformation Output File Paths are platform-specific

Posted: Thu Oct 17, 2019 11:07 am
by ionela
Hi Carolyn,

Thank you for your feedback.

I confirm this path issue is a bug in the current WebHelp implementation. The problem is already logged to our issue tracking tool in order to be analyzed by our development team. I have added your comments to it.


Re: Transformation Output File Paths are platform-specific

Posted: Fri Oct 18, 2019 12:17 am
by csquires
Thanks for the quick response. I'll have to add a script to fix it after the output generates.

Carolyn :)