I'm using RH 9.02. I'm generating some printed documentation of some of our German help content.
One of our chapters I'm generating is fairly small; it only has 56 topics. They're all under a single Heading 2 topic in the TOC. However, for some topics, I'm noticing that only the heading text is generated along with an image, but no body text!
For example, here's some pics of some original topics in RH:
And here's the generated output in Word:
If it helps, here's the contents (in HTML) for the first topic "Endnummer":
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Adobe RoboHelp 9" />
<link rel="StyleSheet" href="../Pcdmis40.css" type="text/css" />
<style title="hcp" type="text/css">/*<![CDATA[*/
<object id="MapCtrl" classid="CLSID:A8ECFBF5-08CC-4065-BD74-0FAD1EA61317"
<h3 style="text-indent: 0in;">Endnummer</h3>
<p class="Figure"><img src="22_flow_files/image003.gif" none;="" border-style:=""
none;"="" alt="" style="border-style: ;" border="0" /></p>
<p class="BodyText">Über das Feld <b><span class="hcp1">Endnummer</span></b>
wird PC-DMIS mitgeteilt, wie oft eine Schleife innerhalb des Werkstückprogramms
zu wiederholen ist. Diese Zahl entspricht in der Regel der Anzahl der
von der Spannvorrichtung gehaltenen Werkstücke (oder Werkstückmuster)
in x- (y- oder z-) Richtung. PC-DMIS fordert außerdem zur Angabe der Startnummer
des Werkstücks (Musters) auf.</p>
<div style="border-top: none; border-left: none; border-bottom: none; border-right: none;
padding: 1.0pt 0in 1.0pt 0in; margin-left: 0.0in; margin-right: 0in;">
<p class="Note"><b style="font-weight: bold;"><span class="hcp1">Beispiel:</span></b>
Es liegen 10 Werkstücke in X- (Y- oder Z-) Richtung vor und Sie möchten
mit der Position Nummer 5 beginnen. Geben Sie 10 (zehn) in das Feld
<b><span class="hcp1">Endnummer</span></b> und 5 (fünf) in das Feld
<b><span class="hcp1">Startnummer</span></b> ein.</p>
<?rh-region_start type="footer" style="width: 100%; position: relative;" ?>
<?rh-cbt_start condition="Online" ?><hr style="color: #d9e4da; background-color: #d9e4da;"
width="300" align="center" /><?rh-cbt_end ?>
<?rh-cbt_start condition="Online" ?><p style="text-align: center;"> <script
<?rh-region_end type="footer" ?>
I'm not excluding any conditional build tags from the output, since this German project was created from a straight .CHM file that was decompiled and imported into RH.
This is frustrating. I cannot trust the output I'm getting when there are such obvious holes, what else is going on that I'm not aware of? German isn't my native language so this is a bit difficult to troubleshoot.
Any idea what's going on? RH 7 had issues in printed output, but at least I knew what they were.
Thanks in advance to any ideas you have.
I believe this is happening because your Image Tag is not resolved properly,. hence it is overlapping the following text content, that makes you get incomplete output in printed doc.
Can you try to replace this Text in Above HTML--
<img src="22_flow_files/image003.gif" none;="" border-style:=""
none;"="" alt="" style="border-style: ;" border="0" />
And generate the Printed Documentation for Word output.
Hope this helps.
Thanks Anjaneai. This was indeed the problem. Unfortunately, from what I can tell, this is caused by a bug in RH 9 when creating a new RH project using our translated files.
In our localization process, we created a CHM in RH 7, then we decompiled the CHM and sent the decompiled files off to localization. The HMTL image tag we got back from our translators, prior to creating the RH 9 project was good as shown in a standard text editor (Notepad++):
But, after creating a RH 9 project from these files, the image tag, as you noticed, is screwed up to this:
Looks like I'll have to go back to RH 7 to regenerate the printed output until they can come up with a fix.
And yes, I know we're using a rather backwards localization process, and should be localizing the RH project directly instead of decompiling, creating new projects etc. We're slowly working on that.
I dont know how wide-spread this issue is. I tried this same chapter in our Portuguese project, and the text in this same chapter seems to export fine. Maybe there's just something weird with my German project...
I am glad that it fixed the problem at your end too.
I believe this problem to be specific to the scenario you are currently working with your project. Because I tried to reproduce with a test project, but failed to make it happen.
Yes, you are correct, decompiling the CHM and then extracting the contents out of it is not a part of standard import process with RoboHelp and I assume this could have cause the tags to alter at your end for the image some how.
Europe, Middle East and Africa