WebHelp: Content area restricted when generating from one specific map

[jlm05]

All of our online maps are created from the same template and use all of the same settings to generate WebHelp.

However, for one specific online map, when I generate the WebHelp, the height of the content area is restricted to about one third the available height in the browser. I can expand the the contents to the full browser height, but the content area height remains restricted.

I cannot find anything in the online map or the initial topic that would restrict the height of the output.

As a (possibly unrelated) side note, the index also won't display in the output for this map, where it does for all of the other maps.

Any ideas of where to look?

Thanks,

Janice

Reply

[jlm05]

The log file for this particular book ends with the following:

[genwebhelp-param] Error
[genwebhelp-param]  SXXP0003: Error reported by XML parser: Premature end of file.

BUILD FAILED
C:UsersJMANWI~1AppDataRoamingSoftQuadXMETAL~1DITA_OTbuild.xml:486: The following error occurred while executing this line:
C:UsersJMANWI~1AppDataRoamingSoftQuadXMETAL~1DITA_OTdemowebhelpbuild.xml:70: The following error occurred while executing this line:
C:UsersJMANWI~1AppDataRoamingSoftQuadXMETAL~1DITA_OTdemowebhelpbuild.xml:79: The following error occurred while executing this line:
C:UsersJMANWI~1AppDataRoamingSoftQuadXMETAL~1DITA_OTdemowebhelpbuild.xml:163: Webhelp index file build error

I've gone through all of the source files, but can't figure out what it is choking on.

Janice

Reply

[Derek Read]

Best to submit this as a support case to XMetaL Support and include all the files. Let them know which version of XMetaL Author Enterprise you are running (see Help > About XMetaL Author Enterprise… for the full version number).

Alternatively (which is what XMetaL Support will end up doing anyway) do the following:
1) Open your map in Tags On view (aka: “XML View of Map”)
2) Repeat:
 a) Remove 1/2 the elements in the map (this is why Tags On is best as you can select many topicrefs at once).
 b) Generate output.
 c) If the output has the issue then the 1/2 you left in is triggering the issue. Cut that 1/2 in 1/2 and repeat. Otherwise, restore the 1/2 you cut out and then cut it in half. Note: You can restore topicref elements you removed (even after save) using Undo in Tags On view.

Once you narrow this down to a specific topic (assuming that is the trigger) you can concentrate on trying to find out what is unique about it.
Note that if you submit this to XMetaL Support they will be performing testing with an unmodified copy of the DITA OT (as installed with XMetaL Author Enterprise).

Reply

[jlm05]

Thanks, Derek.

I was able to use this method to track down the issue to a duplicate “see” index entry. Or at least deleting the second instance of the index entry fixed the problem.

Janice

Reply

[Author]

Posts