Oxygen XML Forum

Hi,

Not quite sure why but when I try to build a DITA map to WebHelp, the transform fails even though I can successfully build to XHTML and CHM. In the result log, I get this message, which seems strange as I am successful with other DITA2HTML transforms.

dita.inner.topics.webhelp:
[xslt] Transforming into C:\HP\out\webhelp
[xslt] Processing C:\HP\temp\webhelp\oxygen_dita_temp\B_test.xml to C:\HP\out\webhelp\B_test.html
[xslt] Loading stylesheet C:\Program Files\Oxygen XML Editor 14\frameworks\dita\DITA-OT\plugins\com.oxygenxml.webhelp\xsl\dita2webhelp.xsl
[xslt] : Warning! Stylesheet module file:/C:/Program%20Files/Oxygen%20XML%20Editor%2014/frameworks/dita/DITA-OT/plugins/net.sourceforge.dita4publishers.common.xslt/xsl/lib/relpath_util.xsl is included or imported more than once. This is permitted, but may lead to errors or unexpected behavior
[xslt] : Warning! Stylesheet module file:/C:/Program%20Files/Oxygen%20XML%20Editor%2014/frameworks/dita/DITA-OT/plugins/com.oxygenxml.webhelp/xsl/relpath_util.xsl is included or imported more than once. This is permitted, but may lead to errors or unexpected behavior
[xslt] C:\Program Files\Oxygen XML Editor 14\frameworks\dita\DITA-OT\xsl\xslhtml\dita2htmlImpl.xsl:4374: Fatal Error! Values of 'standalone' and 'omit-xml-declaration' conflict

Am I missing something? This happens regardless of the type of DITA map.

Hello,

What Oxygen build number do you use? You can find the build number in the Help -> About dialog box. Did you modify any stylesheet from the C:\Program Files\Oxygen XML Editor 14\frameworks\dita\DITA-OT directory? Did you customize the DITA-OT installation from this directory? Did you set any parameter in the DITA Map Webhelp transformation dialog box to a value different than the default one? What is that custom value?

Please send a set of sample files for reproducing the error: a sample DITA map and the included XML topics.


Regards,
Sorin

Sorry. I should have remembered to add that information. The version of oXygen is XML Author 14.2, build 2013021115. There are no modifications to the OT bundled with the product. args.copycss = yes args.css = (path to css). args.hide.parent.link = no, args.xhtml.classattr = yes, webhelp.footer.include = yes.

Looking at this now, it's possible that I didn't add the footer file definition but should this cause the build to fail? At worst, it should return an error and still produce output.

I will email a sample separately.

Hello,

If you set only the webhelp.footer.include parameter you do not set the webhelp.footer.file parameter a default footer will be included in each topic. The transformation will not end with error.

I tried with the same parameters but I did not get an error. Please send the content of the DITA OT view that contains all the output messages of the DITA transformation.

Can you send a sample DITA map with all necessary topics for testing? You can run the action Validate and Check for Completeness on the sample map before sending it.


Regards,
Sorin

I've already sent the sample files. I'll run the transform again and send the results of the log shortly.

Hello,

Thank you for the log file. The sample files are incomplete so it would be great if you can send a sample DITA map with all the included topics so that we do not get errors of type File ... does not exist or cannot be loaded. and [topicpull] [DOTX031E][ERROR]: The file ... is not available to resolve link information.. You can run the action Validate and Check for Completeness on the map in the DITA Maps Manager view to catch these errors.

With the 4 topic files that you sent I did not get the error Values of 'standalone' and 'omit-xml-declaration' conflict. Did you have only these same 4 topic files in the directory of the DITA map when you obtained this error? Maybe sending a complete working map as a sample will help me reproduce the error.


Regards,
Sorin

Unfortunately, I do not have those other files. I will say that for this same set of files the WebHelp builds in 13.2 but does not in 14.2. I tried a different set of files and ran into the same issue - builds in 13.2 but fails in 14.2. I also have users who report that WebHelp doesn't build in 14.2 but does in 14.1.

I tried a different set of files in 13.2 and 14.2 with the base WebHelp transform with no modifications. 13.2 runs, 14.2 fails. I'll package up this set of test files along with the images used (though you'll probably have to redo the image references) into a single package for your use and send via email as soon as I can.

Thank you, that will be great.

Unfortunately I did not get the error Values of 'standalone' and 'omit-xml-declaration' conflict with the DITA Webhelp transformation on your DITA map with 4 topics and many missing references in Oxygen 14.2 build number 2013021115. For fixing the error I have to obtain it first. Actually I never got this error on any DITA Webhelp transformation that I tested in Oxygen 14.2 (and previous versions). I don't know what I am missing yet, I will try again with your new set of sample files.

Did you customize the built-in Webhelp transformation? Did you set any custom value for any parameter?


Regards,
Sorin

The last test I ran was with the base transforms. Not sure why this is happening and am going to restructure the references so that all the image references are to the same folder as an attempt to minimize any other folders in the build.

Even with the images in the same folder, the transform dies in 14.2. Do I need to download the package again?

Just downloaded and installed the latest build and problem is gone.

This is strange. I was able to run for quite a while and now it's failed again with the same problem. I'm not sure what's happening but something seems to get corrupted after a while. Going to try reinstalling again to see what happens.

Reinstalled and the problem went away but I'm now wondering if it'll return. Not sure why this is happening but I ran a number of WebHelp builds before it occurred again.

I don't know, it is strange and I don't get this problem. Please let us know if the problem returns.


Regards,
Sorin

The problem came back. It's unclear why. I don't get the issue with these same files in 13.2.

Hello,

What is your Windows version and build number? Did you install the Oxygen 14.2 for 32 bit Windows or for 64 bit Windows?

Do you get the error with the built-in DITA Map Webhelp transformation (that is no customized stylesheets, no custom parameters set in the transformation dialog) after running it several times on the same XML topic source files, that is the new_hp_styles.ditamap that you sent by email and the four included topics?

It is very strange if you don't get the error the first and second time when you run the transformation on a map, you don't modify the XML source files or the Webhelp transformation, but after running it several times you start getting the error Values of 'standalone' and 'omit-xml-declaration' conflict which stops the transformation. I am not sure yet how we should tackle this.


Regards,
Sorin

I'm running XP Professional Service Pack 3. The problem is now consistently occurring, even after reinstalling. I I downloaded the 32-bit version but I can download and reinstall again. I'm getting this error on both new_hp_styles.ditamap and the second test document I sent you, testy.ditamap. I even flattened out the directory structure so that the images referenced are in the same directory so there are no unresolved references anywhere.

It doesn't matter if I use the base WebHelp or a modified scenario, It seems to fail at all times.

Hello,

Unfortunately I don't get the error with the omit-xml-declaration/standalone attribute conflict with new_hp_styles.ditamap, with testy.ditamap or with any other DITA map. I will have to think about how this error could happen and how I could get it on my Windows computer too.


Regards,
Sorin

Is there any conflict caused by running different versions of oXygen on the same machine?

There is no conflict between two different versions of Oxygen running on the same machine. Each uses a different set of user preferences and they do not communicate when running.


Regards,
Sorin