Oxygen XML Forum

Hi!
I'm a confessed DITA novice - this might be a complete lamer problem, but I can't figure it out and haven't found a solution online.

I'm trying to generate DITA-OT Webhelp out of Oxygen 16.0, build 2014070913
(default XML Schema version 1.1, engine Xerces)

the header of my .ditamap is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map processing-role="normal" xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/">

DITAArchVersion 1.2

I haven't specialized any topics or loaded any custom DTDs, I just want vanilla Webhelp, no frills (for now).

In the output, the TOC bar is more-or-less OK, but none of the links work, search doesn't work, and none of the content is displayed.

In the Transformation problems dialog I've got DOTJ013E errors for all of my .dita topics, and I'm stumped as to why.

If I validate and check for completeness with the default settings, I get tons of the following error for my .png's:
Description: Resource "file:/C:/Users/balazs.bujna/Documents/SVN/docs/Reference/images/mobileFormLanguage_helloTextboxSizeSmall.png" is referenced with incorrect path capitalization.
I have no idea what 'incorrect capitalization' means, as the paths are all correct for the files, and '\'s have been replaced with '/'s.

Can anyone help me out?
Do you need any more info?
Thanks in advance.
Balázs

bujna wrote:In the Transformation problems dialog I've got DOTJ013E errors for all of my .dita topics, and I'm stumped as to why.

This type of error says that the referenced file (all of your .dita files, in your case) can't be read from disk. Please check all the file paths in the href attributes of the topicref elements (or whatever elements your DITA map uses for including the DITA topics in the map). It may be the same problem as with the PNG images: the actual directory name or file name on disk uses small letters (a, b, c, etc.) while the href value in the DITA map uses capital letters (A, B, C, etc.), or viceversa. The same capitalization in directory and file names must be used in the DITA map as in the Windows file system, as available in the Windows Explorer application.

Or it may be a case of outright incorrect file paths in the href attributes in the DITA map, namely file paths that do not exist on disk. You can check that for example by opening the map file in Text editing mode in Oxygen, placing the cursor inside the href attribute value (a file path that refers to a .dita file) and pressing Ctrl+Enter (or alternatively right click and select the action Open -> Open File at Caret). If this action reports an error then the file path in the href attribute does not exist on disk.

bujna wrote:If I validate and check for completeness with the default settings, I get tons of the following error for my .png's:
Description: Resource "file:/C:/Users/balazs.bujna/Documents/SVN/docs/Reference/images/mobileFormLanguage_helloTextboxSizeSmall.png" is referenced with incorrect path capitalization.
I have no idea what 'incorrect capitalization' means, as the paths are all correct for the files, and '\'s have been replaced with '/'s.

'Incorrect capitalization' means that the file path used in the .dita files to include the image file uses small letters (a, b, c, etc.) while the actual directory and/or file names on disk use capital letters (A, B, C, etc.), or viceversa. Please make sure the file paths are consistent.

If this does not fix the errors please send us a small set of sample files (a zip archive) that show all types of errors that you get: a sample DITA map together with all DITA topic files and image files included in this map. Please keep the same directory structure as in your project.

Thank you for the prompt reply.
Turns out the problem was that instead of the complete absolute file path to the referenced image or code sample, Oxygen needed a relative file path, with the part of the file path that the .dita files and the .png files share replaced by '..'.
To complicate matters, Oxygen apparently considers every .dita file inside the .ditamap unparseable if it encounters parsing problems in any of them.
As for the capitalization problems, upon close scrutiny, some of the href's and actual file paths don't actually match, so it's my bad.
Things seem to be back on track again, thank you.
Will post another reply to clear things up for future reference when I'm done.

bujna wrote:Turns out the problem was that instead of the complete absolute file path to the referenced image or code sample, Oxygen needed a relative file path, with the part of the file path that the .dita files and the .png files share replaced by '..'.

All the files and resources included in the DITA map should be located in the same directory as the DITA map or one of the sub-directories of this directory. This is a requirement of the DITA-OT toolkit. Oxygen includes a fix for the case of the topic files or resource files located outside the DITA map directory (which is not activated by default in the DITA transformations), but the general recommendation for DITA authors is to not place them outside this directory.

bujna wrote:To complicate matters, Oxygen apparently considers every .dita file inside the .ditamap unparseable if it encounters parsing problems in any of them.

Parsing errors that are show-stoppers for the DITA topic processing must be reported to the user. In your case they were stopper errors, so they must be reported. Only the unparseable DITA files are reported as errors.


Thank you for letting us know,