Missing Index Entries in Printed Documentation

Hello All,
Using RoboHelp X5 to generate a Web Help File and
corresponding Printed Documentation. Within the Web Help file there
are index extries which are linked to a topic. Within the topic are
bookmarks which also link to index entires.
When I generate the Printed Documentation, only index entries
linked to a topic appear, those entries linked to a bookmark do not
appear.
How do I generate the Printed Documentation and have all the
index entries (topic and bookmark linked) appear?
Thanks

This is to confirm that if you use bookmarks (the little
white flag icons) in your topics, then drag them under an Index
keyword in the Index designer, they definitely WILL NOT show up in
the printed docs. To solve the problem, I created separate topics
so there wouldn't be a need to bookmark (which I did because the
user would have had to scroll to view the whole page), then linked
the keywords to those topics.

Similar Messages

Missing index entries

I have been working on a massive index (about 20,000 entries) on a ID CS6 document, a 700 page biological work of reference where all taxon names should be indexed. Took me several weeks. I produced the InDesign file from a Word file, but entered the index entries in InDesign (there weren't any in the Word file).
Now I found that many of my entries seem to have gone missing. They do not appear in the generated index. On the page where I entered it, the normal code (a ':' above a '^') is changed in a single ':'. I fear the last code, ':', means something like 'invalid marker', because they also appeared in another (crashed) CS6 document where they represented corrupted MS Word cross references (see "Cross references from a Word file", a still unanswered question on this forum). Normally when you select an index marker, the entry is highlighted in the Index Window. When I select the ':', nothing happens.
In the beginning of the book, I just marked any singular taxon name, but as it appeared that some taxon names appeared quite often, I started using the 'Add all' button in the index entry window. (I hope I use the right English names, they appear in Dutch for me.) This meant that some taxon names on earlier pages got double markers, but I thought that was no problem because the same markers on the same page only result in one entry in the generated index file. Could this be the bug that's biting me? I haven't found the problem in the later pages of the book.
A lot of the entries still found their way to the generated index, but of course I find this very worrying. Because I still have to process many author corrrections, I will have to generate the index again.
So, I have the following urgent questions:
-     Why does this problem occur, under which circumstances? Will regenerating the index result in more loss of entries?
-     Can those ':' markers corrupt my file in any way? What are they? (With the "cross reference problem", after some time I was unable to open the file again, which would with this project give me a major problem.)
-     Can I somehow 'revive' the missing entries automatically? Or is there at least a way to search for the ':' markers? (They are hardly visible.)
-     How can I prevent this from happening in the future?

Forum participants are not Adobe employees. We're users like you who volunteer to share what we know.
Thanks for the added details.
Usually someone somewhere in the forum's global audience is awake and eager to participate at almost any hour. However, "super storm" Sandy in the USA has caused massive losses of power, transportation, and communication, so responses may be delayed for some time.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices
Fritschy wrote:
Thanks for your compliments, although they don't bring me any further.
The version is 8.0.1, I always update when I'm prompted to do so by the update centre. As far as I know it is an international version.
Still, I would guess the InDesign developers could tell me something about that ':' marker. I suppose the software didn't invent it itself.

Missing Index entries after Migrating Repository from 1.3.2 to 9i

Hi,
We have migrated our repository from 1.3.2 to 9i.
Index entries were created for both the Primary keys and Foreign keys.The indexes were created by us and not by designer.
After migration to 9i the index entries for primary and Foreign are missing in the design editor.When we generate a table we get an error because these index entries are missing.
Does designer 9i support index entries?Or How are indexes handled by designer 9i?

To clarify, your index entries were in the database but NOT defined in Des 1.3.2 model? Because if they were in the model, then I'd look back at your intermediate migration definitions to make sure the indexes were still defined properly in there.
In Des 2.1/6.0/6i/9i/10g, Indexes are a separate sub-element (SACs) for a Table Definition. They don't have to be associated with a key structure. And in newer database versions, a PK / UK has an implicit index constructed for it in the database, so Designer doesn't bother showing you the Index in the model. Just the PK or UK itself (again, these are also separate SACs).
And it's not clear where you're getting the error. During the generate? Or during the instantiation into a database? Neither situation is a common fault.

Index Entries in 9i

Hi,
In older versions of designer 1.3.2 Index entries are
available for foreign keys.
We have migrated the repository from 1.3.2 to 9i and Index entries are not available in the design editor for foreign keys.When we generate a table in 9i we get error messages because of missing index entries.
What about Primary keys?Does designer generate Index entries for Primary keys also??
Kindly Help.

To clarify, your index entries were in the database but NOT defined in Des 1.3.2 model? Because if they were in the model, then I'd look back at your intermediate migration definitions to make sure the indexes were still defined properly in there.
In Des 2.1/6.0/6i/9i/10g, Indexes are a separate sub-element (SACs) for a Table Definition. They don't have to be associated with a key structure. And in newer database versions, a PK / UK has an implicit index constructed for it in the database, so Designer doesn't bother showing you the Index in the model. Just the PK or UK itself (again, these are also separate SACs).
And it's not clear where you're getting the error. During the generate? Or during the instantiation into a database? Neither situation is a common fault.

Generated index is missing indexed items

Working with book and separate chapter for index. Index generates but is missing index entries. Is it something I'm doing or an InDesign problem?

Thanks for input. All available updates have been applied. Long telcon with India so far has produced no cure but at last they are 'escalating' problem to find a solution. It seems to only happen in the 'Symbols' heading (non-alphabetic entries) of the index. Not only are items missing but reference page numbers are missing and/or scrambled. Looks like several indexed subjects are loosing page references and/or picking up page references from following index lines. If you can read the image attached you'll see what I'm talking about if you compare the index flyout lines with what shows up in the generated index. Quite a time consuming pain. It took me almost an hour on the phone to get India to the point they wanted to see this.

Index entries missing in .chm but are present in the printed version

This is strange.
I have a number of index entries as follows:
troubleshooting/file problems
troubleshooting/login problems
troubleshooting/printer problems
These appear in the .docx (Word) version, which is what I've been using for the review cycle. Today, though, I had the .chm open and I noticed that the entire group of troubleshooting\ entries aren't in the .chm!
I recompiled the HTML Help, just in case I was looking at an old version and no, they're not there.
I searched for them in the Index tab, thinking maybe they were somehow out of order, but they're truly not there.
Any idea what could be causing this? I'm using RoboHelp 9.

I don't know how to apply conditional build tags against an index, so I didn't do that -- at least not deliberately
I looked at the HTML, the Advanced tab in Topic properties, and the TOC page properties. I don't see anything there that looks like a Condition setting. I looked at the HTML externally (that is, went to Windows Explorer and double-clicked the file and then looked at the HTML source). Couldn't see anything. I launched the .chm file and then looked at the HTML for that topic. Still couldn't see anything.
I opened the .hhk file and I can see the entries for troubleshooting, I believe. Here is what I see:
<item name="troubleshooting">
        <item name="file problems">
            <section name="Release Information" link="Release_Information.htm">
            </section>
        </item>
        <item name="printer problems">
            <section name="Printing Problems" link="Printing_Problems.htm">
            </section>
        </item>
        <item name="checkerboard">
            <section name="Checkerboard Pattern in Window" link="Checkerboard_Pattern_in_Window.htm">
            </section>
        </item>
        <item name="screen display">
            <section name="Checkerboard Pattern in Window" link="Checkerboard_Pattern_in_Window.htm">
            </section>
        </item>
        <item name="login problems">
            <section name="Login Problems" link="Login_Problems.htm">
            </section>
        </item>
        <item name="misc problems">
            <section name="Other Problems" link="Other_Problems.htm">
            </section>
        </item>
        <item name="Reporting Services Reports">
            <section name="Reporting Services Reports Problems" link="Reporting_Services_Reports_Problems.htm">
            </section>
        </item>
        <item name="sorting problems">
            <section name="Sorting Incorrectly" link="Sorting_Incorrectly.htm">
            </section>
        </item>
    </item>

Missing topics in printed documentation

I am using RoboHelp V7 and WebHelp as my Primary Layout. My project has approximately 100 topics.
The project is basically an A-Z with various topics saved into 26 folders (A-Z). The printed documentation prints perfectly except that the H1 headings for all the 'A' topics are missing from the resulting Word document.
The table of contents in the Word document is correct, with "A" listed but none of the topics are listed in the TOC. The topics appear in their correction location in the word document except the H1 headings is missing. The heading "A" appears in the correct location in the Word document.
In each topic the H1 is in the header and draws its text from the name of the topic.
All the 'A' topics were created manually and the rest 'B-Z' were imported from an Word Document. This appears to be the only difference between the topics!!
All the topics (A-Z) are connected to the same template and access the same CSS file.
On the final screen of the Print Documentation Wizard (Print Document Appearance - Pninted Documentation) I have tried connecting to different templates from the drop down list under MS Word Template. I have also created my own *.dot file out of a resulting document (i.e. stripping all the text and saving as *.dot). But no luck.
Any thoughts?
Many thanks in anticipation.

The HMTL for the two types of pages looks identical
An 'A' page
<div placeholder id=header style="width: 100%; position: relative;">
<h1><variable name=title x-format=default x-value="Air conditioning">Air conditioning</variable></h1>
</div>
A 'D' page
<div placeholder id=header style="width: 100%; position: relative;">
<h1><variable name=title x-format=default x-value="dress code">dress code</variable></h1>
</div>
The only obvious difference in the HTML for the two types of pages is that the pages imported from Word have the following line in their metadata:
<meta name=OriginalFile content="Orientation Guide - Draft Wording_V2.doc">
And both types of pages are clearly connected to the same style sheets.
Stumped?

Order of Index and Glossary in Printed Documentation

In my RoboHelp HTML project, I'm adding an Index and Glossary to the Printed Documentation section layout. I want both files below the Chapter Layout icon. They both will go no further than the first icon above the TOC. The down arrow is grayed out.
Someone else had this problem, and the answer was to click the last icon in the Section layout and then add the files. This did not work for me.
Any ideas?
Thanks in advance.

I had the same problem with RH8.
What corrected it for me was to delete the TOC, click the + button, add the Index (it magically appeared where it was supposed to be, at the end), then click the + button again to add the TOC back in. (I don't have a Glossary in my section layout)

Missing configuration entry for data - index relationship

IN ST04 -> configuration -> Data Class
all data classes are in yellow I'm trying to activate them and getting the following error
"Missing configuration entry for data - index relationship"
This is the result of a system copy
Thanks
Kkhaldoun

Hi All,
Just an update, I was able to get around my problems by patching the 2004s media from sp6 to sp8, uninstalling my scs, and database and re-installing from the patched media.

Unable to Generate Printed Documentation in PDF Format

This past week I started having a consistent error when attempting to generate a Printed Documentation layout. This error reads "Internal error encountered, Failed to generate Printed Documentation." Prior Printed Documentation builds on this same project completed fine. Nothing was done to the Help project between the times when this worked and when it no longer was able to create Printed Documentation.
I receive this error even if I generate an entirely new "blank project" build, and then attempt to create a Printed Documentation build from this new blank project. Researching this error, I see this has been a reoccuring problem with this product for some time. The few threads that list the problem as having been "fixed" provide resolution steps that have not worked in my case. Right now I am waiting for our IT Helpdesk people to re-install the Suite. Hopefully this will resolve this problem.
Additional information on this problem - PDF Printed Documentation is failing - the HTML build works fine. If I select just a .DOC Printed Documentation output, this also works correctly. The resulting Word document looks good, although hyperlinks do not work within this Word document. I have reloaded Office 2003 as a troubleshooting effort, but this has nbot resulted in any change in symptoms.
The entire error text is enclosed below, although several other people have also done this in past entries. The few lines that read "Warning, and then report a style issue is NOT the problem here. As stated earlier, when I do this same Printed Documentation build on an entirely new "blank project" it does not work, and the Output text in that case does not contain any such "Warnings" about Styles.
Error text below:
Starting to build Printed Documentation...
Printed Documentation processor 8.0.1.204
Building C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.doc ...
Preparing to create Printed Documentation...
Clearing output folder...
Preparing files for Print Document...
Copying files...
Updating files...
Finished preparing in 2 seconds.
Preparing environment...
Printed Document Generator Environment: Word 11.0.8313, OS 5.1.2600, RAM 2048 M Bytes
Building Printed Documentation 'Printed Documentation'...
Building Single Document 'Printed_Documentation.doc'...
Building 'RF-7800V-HH About this Help'...
Building 'Table of Contents'...
Preparing to build chapters...
Building 'RF-7800V-HH Help and Support'...
Processing 'RF-7800V-HH Welcome'...
Building 'RF-7800V-HH RSP Help'...
Processing 'RF-7800V-HH Station Information'...
Building 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Anc. Connector Mode'...
Processing 'RF-7800V-HH No-Sync Beeps'...
Processing 'RF-7800V-HH Power Management'...
Processing 'RF-7800V-HH Retransmit'...
Processing 'RF-7800V-HH USB Mode'...
Processing 'RF-7800V-HH Broadcast Gateway'...
Processing 'RF-7800V-HH IP Routing'...
Processing 'RF-7800V-HH Voice Settings'...
Processing 'RF-7800V-HH Time and Date Settings'...
Processing 'RF-7800V-HH Position Reporting'...
Processing 'RF-7800V-HH User Interfaces'...
Processing 'RF-7800V-HH Net Switches'...
Processing 'RF-7800V-HH Ethernet Interface'...
Building 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Radio Passwords'...
Processing 'RF-7800V-HH GPS'...
Processing 'RF-7800V-HH Locksets'...
Building 'RF-7800V-HH Network Types'...
Processing 'RF-7800V-HH Network Types'...
Building 'RF-7800V-HH Fixed Frequency LOS'...
Processing 'General Information - Fixed Frequency LOS'...
Processing 'RF-7800V-HH FF Network Information'...
Processing 'RF-7800V-HH FF Preset'...
Processing 'RF-7800V-HH FF General'...
Processing 'RF-7800V-HH FF Comsec'...
Processing 'RF-7800V-HH FF Data-Voice'...
Processing 'RF-7800V-HH FF Squelch'...
Processing 'RF-7800V-HH FF Advanced'...
Warning: style (p.Heading7) is not defined and will be mapped to 'Normal'.
Building 'RF-7800V-HH Quicklook'...
Processing 'General Information - Quicklook'...
Processing 'Hopset Creation - Quicklook'...
Processing 'RF-7800V-HH QL Network Information'...
Processing 'RF-7800V-HH QL Preset'...
Processing 'RF-7800V-HH QL General'...
Processing 'RF-7800V-HH QL Comsec'...
Processing 'RF-7800V-HH QL Data-Voice'...
Processing 'RF-7800V-HH QL Advanced'...
Building 'RF-7800V-HH Sample Plans'...
Processing 'General Information - Sample Plans'...
Processing 'Simple Fixed and Quicklook Nets'...
Processing 'Single Fixed and Quicklook Nets'...
Processing 'RF-7800V-HH Manage Keys'...
Processing 'RF-7800V-HH Program Radio'...
Building 'RF-7800V-HH Tech Support'...
Processing 'RF-7800V-HH Technical Support'...
Processing 'RF-7800V-HH Radio Firmware Compatibility'...
Building 'FAQs'...
Processing 'RF-7800V-HH FAQ Index'...
Processing 'FAQ 01'...
Warning: style (span.strong) is not defined and will be removed.
Warning: style (p.para) is not defined and will be mapped to 'Normal'.
Processing 'FAQ 02'...
Processing 'FAQ 03'...
Processing 'FAQ 04'...
Processing 'FAQ 05'...
Processing 'RF-7800V-HH Glossary'...
Warning: style (p.FM_CellRowHead) is not defined and will be mapped to 'Normal'.
Warning: style (span.Glossary) is not defined and will be removed.
Warning: style (p.FM_CellBodyLeft) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_GLOSSARY) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_Para) is not defined and will be mapped to 'Normal'.
Completed building chapters...
Building 'Index'...
Updating list paragraphs...
Updating images...
Updating page numbers...
Updating page headers...
Updating Table of Contents...
Updating Index...
Saving 'Printed_Documentation.doc'...
Generating 'Printed_Documentation.pdf'...
Failed the generate PDF file 'C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.pdf'...
Failed to save 'Printed_Documentation.doc'...
Cleaning up temporary files...
I am pretty sure nobody will have any fix suggestions that work to solve this problem, but I am making this entry for historical purposes. I will add an entry stating whether the Suite reload resolves this issue.
Thanks,
Tim C @ Harris

If I select ONLY the Word DOC Output format in the Printed Documentation
setup, the output is created without an error (output text below). Links do work within
this Word document (a symptom change since installing patch 8.0.2).
When I use this Word document to create a PDF (using the Adobe PDF
printer driver) a PDF is successfully created, however no bookmarks are
created in the bookmarks panel and none of the links in this PDF work
(although they are created looking like they will work, i.e., blue
underlined text).
Regards,
Tim
------------- Output Text --------------------------
Starting to build Printed Documentation...
Printed Documentation processor 8.0.1.204
Building C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.doc ...
Preparing to create Printed Documentation...
Clearing output folder...
Preparing files for Print Document...
Copying files...
Updating files...
Finished preparing in 3 seconds.
Preparing environment...
Printed Document Generator Environment: Word 11.0.8313, OS 5.1.2600, RAM 2048 M Bytes
Building Printed Documentation 'Printed Documentation'...
Building Single Document 'Printed_Documentation.doc'...
Building 'RF-7800V-HH About this Help'...
Building 'Table of Contents'...
Preparing to build chapters...
Building 'RF-7800V-HH Help and Support'...
Processing 'RF-7800V-HH Welcome'...
Building 'RF-7800V-HH RSP Help'...
Processing 'RF-7800V-HH Station Information'...
Building 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Features'...
Processing 'RF-7800V-HH Anc. Connector Mode'...
Processing 'RF-7800V-HH No-Sync Beeps'...
Processing 'RF-7800V-HH Power Management'...
Processing 'RF-7800V-HH Retransmit'...
Processing 'RF-7800V-HH USB Mode'...
Processing 'RF-7800V-HH Broadcast Gateway'...
Processing 'RF-7800V-HH IP Routing'...
Processing 'RF-7800V-HH Voice Settings'...
Processing 'RF-7800V-HH Time and Date Settings'...
Processing 'RF-7800V-HH Position Reporting'...
Processing 'RF-7800V-HH User Interfaces'...
Processing 'RF-7800V-HH Net Switches'...
Processing 'RF-7800V-HH Ethernet Interface'...
Building 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Global Settings'...
Processing 'RF-7800V-HH Radio Passwords'...
Processing 'RF-7800V-HH GPS'...
Processing 'RF-7800V-HH Locksets'...
Building 'RF-7800V-HH Network Types'...
Processing 'RF-7800V-HH Network Types'...
Building 'RF-7800V-HH Fixed Frequency LOS'...
Processing 'General Information - Fixed Frequency LOS'...
Processing 'RF-7800V-HH FF Network Information'...
Processing 'RF-7800V-HH FF Preset'...
Processing 'RF-7800V-HH FF General'...
Processing 'RF-7800V-HH FF Comsec'...
Processing 'RF-7800V-HH FF Data-Voice'...
Processing 'RF-7800V-HH FF Squelch'...
Processing 'RF-7800V-HH FF Advanced'...
Warning: style (p.Heading7) is not defined and will be mapped to 'Normal'.
Building 'RF-7800V-HH Quicklook'...
Processing 'General Information - Quicklook'...
Processing 'Hopset Creation - Quicklook'...
Processing 'RF-7800V-HH QL Network Information'...
Processing 'RF-7800V-HH QL Preset'...
Processing 'RF-7800V-HH QL General'...
Processing 'RF-7800V-HH QL Comsec'...
Processing 'RF-7800V-HH QL Data-Voice'...
Processing 'RF-7800V-HH QL Advanced'...
Building 'RF-7800V-HH Sample Plans'...
Processing 'General Information - Sample Plans'...
Processing 'Simple Fixed and Quicklook Nets'...
Processing 'Single Fixed and Quicklook Nets'...
Processing 'RF-7800V-HH Manage Keys'...
Processing 'RF-7800V-HH Program Radio'...
Building 'RF-7800V-HH Tech Support'...
Processing 'RF-7800V-HH Technical Support'...
Processing 'RF-7800V-HH Radio Firmware Compatibility'...
Building 'FAQs'...
Processing 'RF-7800V-HH FAQ Index'...
Processing 'FAQ 01'...
Warning: style (span.strong) is not defined and will be removed.
Warning: style (p.para) is not defined and will be mapped to 'Normal'.
Processing 'FAQ 02'...
Processing 'FAQ 03'...
Processing 'FAQ 04'...
Processing 'FAQ 05'...
Building 'RF-7800V-HH Glossary'...
Warning: style (p.FM_CellRowHead) is not defined and will be mapped to 'Normal'.
Warning: style (span.Glossary) is not defined and will be removed.
Warning: style (p.FM_CellBodyLeft) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_GLOSSARY) is not defined and will be mapped to 'Normal'.
Warning: style (p.FM_Para) is not defined and will be mapped to 'Normal'.
Completed building chapters...
Building 'Index'...
Updating list paragraphs...
Updating images...
Updating page numbers...
Updating page headers...
Updating Table of Contents...
Updating Index...
Saving 'Printed_Documentation.doc'...
Completed building Printed Documentation...
Preparing output directory...
Cleaning up temporary files...
Finished Printed Documentation generation in 5 minutes 36 seconds.
Building Printed Documentation complete.

Problems with RH 9, CBT, and Printed Documentation

When I upgrade an x5 project in the new RH9, all appears to go fine until I try to generate the Printed Documentation. I was disappointed that the printed documentation STILL requires so much cleanup. Text tagged with the Online condition sometimes displays on some topics, even when Online is excluded from the output. Also, some of the cleanup issues surrounding headings and index entries are still necessary.
The four biggest issues are:
1) If a "book" TOC heading also has content (a topic associated with it), a double-heading appears in the printed output. You have to manually remove all these extra headings in the cleanup process.
2) All index entries appear in the paragraph BEFORE the actual heading they mark, instead of after the heading, resulting in the Index not being correct (if a heading appears at the top of the page, the Index points to the previous page where the index entry resides, instead of the correct page). I have to manually go through the entire document and move each index entry to the paragraph AFTER the heading it marks.
3) Robohelp ignores the exclusion of Online conditions on some random topics. There is a workaround to "trick" Robohelp, but it takes *a lot* of time to do. To "trick" Robohelp, I had to generate a printed manual and make a list of all topics that "slipped" through. And, then edit each topic where the online condition was ignored, by adding an extra, empty paragraph to the end of each topic that had:
·         a single paragraph of text (aside from header and footer info)
·         ends with bulleted list (and no extra paragraph marker following)
·         ends with a table (and no extra paragraph marker following)
·         ends with a figure (and no extra paragraph marker following)
·         ends with see also\How do I\misc button text (and no extra paragraph marker before the seealso/how do I listings)
4) I noticed that when I opened a topic for the first time in Robohelp, the Online condition sometimes gets applied to incorrectly tagged text (it wasn't tagged this way in the x5 content). This requires me opening each topic in the upgraded project, and checking each topic to make sure the online condition is applied correctly in each one (a very tedious process, especiallly if you have a doc set of over 1 mil words!).
Expected results:
Printed doc does not contain double headings. Index entries appear after headings. Conditional text behaves as it is supposed to behave (and if you tell Robohelp to exclude the ONLINE condition, it does it for ALL topics).
Does anyone have any suggestions/recommendations for this? Yes, I have the latest build. We held off on upgrading to previous releases of Robohelp because of the Printed Manual problem too (it seems like each version created more clean up work). :-( I logged a bug on the Adobe forum.Any and all suggestions appreciated. Thanks!

Mr. Grainge,
Thank you so much for your thoughtful answers back! I appreciate you taking time out to write such a thorough reply. I hope Adobe appreciates you! You're number one in follow ups!
Unfortunately, your answers did not solve my problems. But, you did give me some ideas on where the problems could be occurring. So, thank you!! Before I begin: In answer to your question, yes I *am* using the supplied Style Mapping template (I never had luck with the custom one myself). Also, I am going to hold off on replying to 1) and 2), but I'd like to share my answer on 3) and 4), which is really just what I need to get Printed Documentation working in Robohelp 9 the same way it worked in x5.
A little history: I have a set of about 50 help projects that span many versions of our company's product, and multiple versions of Robohelp (some even go back to the 90s!). They even include some help projects that were originally in Frame/WebWorks but were later ported to Robohelp. There's a lot of history to them.
Investigating the Problem: When I opened an x5 project in RH 9, I noticed that some of the timestamps on the .htm files didn't match the rest of the files. It turned out, that these very same files that were the ones giving me problems with the Conditional text! That's when your thoughts about the mapping came to mind...As I said, my project spanned mutiple versions of Robohelp. I wondered if some of the coding on the .htm page was being parsed incorrectly on upgrade, and if if that was the reason why RH couldn't update the pages (which explain the unchanged timestamps). In other words, I wondered if Robohelp was mapping the styles correctly on import. So, I compared these unupgraded .htm files with ones that did upgrade, to see if there was something on the code page that could be causing the problem.
Solution to Fix 3) and 4) above:
I'm going to list out everything that I did below, however, not everything on this list applies to everyone. But, hopefully it will help you, if you ever run into this scenario yourself, and it might give you some ideas on how to get your HTML files working. So, before upgrading, here is what I did:
I opened my old CSS in a text editor and removed all the Robohelp autogenerated comments.
In Homesite, I did a bunch of Search and Replaces on a copy of the older x5 project. I looked for code that may have been generated in an earlier version of RH,and for unusual structures in the meta and style declaration area that could be causing conflicts. Here is a list of my search and replaces below:
Search for:

Replace With:
nothing
Search for:

Replace With:
nothing
Search for:

Replace With:
nothing
Search for:
<p> </p>
Replace With:
nothing
Search for:
<p> </p>
Replace With:
nothing
Search for:
<html>
<head>
Replace With:
<html>



<head>
Search for:

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

<link href="MyHelp.css" rel="stylesheet" type="text/css">

<script language="javaScript" type="text/javascript" src="MyHelp.js"></script>
<script language="javascript" src="eHlpDhtm.js"></script>
</head>

<body TABINDEX=1>
Replace With:

<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=generator content="RoboHELP by eHelp Corporation - www.ehelp.com">
<meta name=generator-major-version content=0.1>
<meta name=generator-minor-version content=1>
<meta name=filetype content=kadov>
<meta name=filetype-version content=1>
<meta name=page-count content=1>
<meta name=layout-height content=597>
<meta name=layout-width content=662>

<link href="MyHelp.css" rel="stylesheet" type="text/css">

<script language=javaScript
type="text/javascript"
src="MyHelp.js"></script>
<script language=javascript
src="eHlpDhtm.js"></script>
</head>

<body TABINDEX=1>
Search for:
<a class=toplinks href="#top"> Top</a>
…or…
<a class=toplinks href="#top">Top</a>
Replace With:
<a class=toplinks
href="#top">Top</a>
Search for:
<h3 id=SeeAlsoTitle
class=SeeAlsoTitle
style="x-condition: Online;">See Also</h3>
<div id=seeAlso
Replace With:
<h3 id=SeeAlsoTitle
class=SeeAlsoTitle
style="x-condition: Online;">See Also</h3>
<div id=seeAlso
After I did these all these search and replaces in the copy of the x5 version of the project, I opened the project again in RH 9 and upgraded it. After the upgrade, I checked the timestamps on the .htm files to make sure they all changed. They did! It worked! Everything upgraded properly this time... I tested the Printed Manual output and no conditional text slipped through this time. Yay!
In Summary:
This is what I learned if you are having problems with Conditional text and Printed Manuals in an upgraded RH project:
Always make backups of your older projects before you upgrade anything. I know this is elementary, but I thought it was worth reminding.
Check the timestamps of the files after you upgrade the project. If there are a group of files with timestamps that aren't similar to the rest of the files, chances are Robohelp was having trouble converting those files.
Try looking at the HTML code in those files and see if anything looks out of the ordinary. Some examples are above.
If you have already ported the RH project and it's too late to go back, go look at the file timestamps anyhow. For all the older files, try opening each one in Robohelp and add a space or something (to force RH to change it), and save it. I didn't have the time to verify this, but it seemed on most instances: when I forced RH to save the file manually, it updated correctly and the problem with the conditional text went away. (This option takes longer, especially if you have to do each page individually, but it's worth a try, IMHO.)
Aside from the initial Printed Manual woes, which are resolved, the upgrade process from RH 9 really was seamless! Best I have ever seen! Everything just works! Awesome is a word that comes to mind.
Printed Documentation output does work on upgrade, but in my opinion is: it is no better than it was before, in previous versions.
I wish there were more fixes to the Printed Manual output. When you have a product help system that spans multiple versions, contains over 2.5 million words, and 10,000+ topics, having a lot of cleanup on the production end is costly. What use to take a person on my team less than a day to generate 50+ PDFs in FrameMaker, takes 4-5 weeks man-time in RH. I will outline my opinions in my next reply to this thread.
Thanks again, Mr. Grainge!

Can not create missing index

Dear all,
This is about a BW 3.5 system running Oracle 10.2.0.2 on Solaris 10
After an online database reorganisation, I receive these messages in db13
BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPR3./BI0/F0BWTC_C02
BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPR3./BI0/F0BWTC_C05
According to the logs, the tables above have been reorganised successfully.
I see the missing indexes in db02 under Missing Indexes:
Secondary indexes               13
    /BI0/F0BWTC_C02-070
    /BI0/F0BWTC_C02-060
    /BI0/F0BWTC_C02-050
    /BI0/F0BWTC_C02-040
    /BI0/F0BWTC_C02-020
    /BI0/F0BWTC_C02-010
    /BI0/F0BWTC_C05-070
    /BI0/F0BWTC_C05-060
    /BI0/F0BWTC_C05-050
    /BI0/F0BWTC_C05-040
    /BI0/F0BWTC_C05-020
    /BI0/F0BWTC_C05-010
    /BIC/FZ_CPLN_00-900
If I try to select one and click on create in db, I get a short dump
Runtime Error          RAISE_EXCEPTION
Date and Time          23.08.2007 11:12:13
ShrtText
Exception condition "STORAGE_NOT_DETERMINATED" raised.
What happened?
     The current ABAP/4 program encountered an unexpected
     situation.
What can you do?
     Print out the error message (using the "Print" function)
     and make a note of the actions and input that caused the
     error.
To resolve the problem, contact your SAP system administrator.
     You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletion
     date.
is especially useful if you want to keep a particular message.
Error analysis
     A RAISE statement in the program "SAPLSDB2" raised the exception
     condition "STORAGE_NOT_DETERMINATED".
     Since the exception was not intercepted by a superior program
     in the hierarchy, processing was terminated.
173   else.
174      storage_source_hierarchy-dbr = 'X'.
175   endif.
176   storage_source_hierarchy-cmt = 'X'.
177   storage_source_hierarchy-cmp = 'X'.
178   if dbtabname ne space and dbtabname ne tabname.
179     perform shdupg_get_index_storage tables storpar
180             using dbsys prid tabname indexname storage_source_hierarchy
181                   dbindex_of_origtable dbprimindex_of_origtable
182             changing rc.
183   else.
184     call function 'DB_STORAGE_GET'
185          exporting
186               dbsys                = dbsys
187               prid                 = prid
188               tabname              = tabname
189               indexname            = indexname
190               dbindex              = realname
191               dbrefindex           = name_of_primidx
192               source_hierarchy     = storage_source_hierarchy
193          tables
194               storpar              = storpar
195          exceptions
196               mapping_error        = 1
197               db_error             = 2
198               uncomplete_parameter = 3
199               others               = 4.
200     rc = sy-subrc.
201   endif.
202   if rc ne 0.
>>>>     raise storage_not_determinated.
204   endif.
205
206 * Progamm generieren
207   perform db_get_progname using 'SDB2F' dbsys changing sdb2fdbs.
208   refresh statements.
209   perform gen_create_index in program (sdb2fdbs)
210           tables ddfldnames storpar loc_stmt
211           using tabname indexname realname unique dbsys rc.
212   if rc <> 0.
213 *KUGL-protocol-270694
214     perform stdo_sam1
215        using prid max_severity msgid '122' realname.
216     raise program_not_generated.
217   endif.
218   statements[] = loc_stmt[].
219
220   perform create_index_finish tables loc_stmt
221                           using tabname realname dbsys no_exec rc.
222 if rc <> 0. raise program_not_generated. endif.
Any ideas?
Many thanks
Andreas

Hi,
Please check following note:
Note 703304.
You may have to import correction against your release.
Regards,
Payal Patel

Missing Index topics, links and .htm files

I hope someone can help with this, as I am very frustrated
right now. I normally use RoboHelpX5, but have also tried this in
RoboHelp7.
If I generate a Winhelp2000 version of our help system,
everything appears normal. All of the specified index keywords are
there, all of the links are there, etc.
But if I generate either HTML or WebHelp versions using the
same source, as I'm supposed to be able to, for some reason:
1. Index entries for certain topics disappear from the list.
If I manually add the topic to the index again and save, then
regenerate the help files, the topic is still missing from the
index.
2. The hyperlinks for the missing items in #1 above do not
appear. The original text is there, but there is no hyperlink. If I
try to add a hyperlink again, the topic appears in the list, but
once I regenerate the help files, the link disappears again.
3. The individual .htm file for the missing items in #1 above
are not being generated.
Is there some reason why these topics are being dropped from
the html and webhelp versions of the help system? Is there some
sort of topic formatting or setting I am missing? I have tried to
compare working topics vs. missing topics, and cannot find anything
different in my Word document formatting.
I have tried creating a completely different help system,
using clean documents with no RoboHelp formatting, and consistently
have problems with the same topics. I even tried on another
computer that had never had RoboHelp on it before. That didn't make
any difference. The topics were still missing from the index, the
hyperlinks to those topics were still missing, and the individual
.htm files were not generated.
Any help would be appreciated.
Stephanie
(ow_mas)

Hi,
I ran into the same problem today with some top level Index
entries not showing up in WebHelp. I discovered how to fix it by
comparing the entries that did show up with those that didn't. If
an entry had a topic associated with it, it showed up; if it has a
cross-reference, it doesn't.
Double click an Index entry in the Index pane (or right click
and choose Properties), then clear the Cross-reference checkbox.
Repeat for each entry that has a cross-reference instead of a
topic. There may be a global way to fix them all, but I haven't
found it yet. Then recompile your help, Voila!
Hope this helps....
Zie3D

Error when trying to create printed documentation in RH 7

Hello,
I've created a WebHelp project in RH 7 that I'm trying to
make a PDF for, as well. An error always appears when trying to
generate printed documentation, even if only the PDF option or the
Word option is selected. RH 7 processes and builds each of the
pages, index, images, etc. It gets to the very end on the status
bar and an error appears that it failed to generate the PDF.
In the output view, I see that it successfully processed
everything until the end when it says (the last four lines are the
error):
Updating Table of Contents...
Updating Index...
Saving 'GVE_Help_.doc'...
Generating 'GVE_Help_.pdf'...
Failed the generate PDF file '(The path is written here but
has been removed for this post)'...
Failed to save 'GVE_Help_.doc'...
Cleaning up temporary files...
Internal error encountered, Failed to generate Printed
Documentation.
Is there any way to get the Printed Documentation to work
properly in RH 7? I receive the same error for any of the WebHelp
projects I've opened in RH 7. I'm using Windows XP and have Word
2003 on my PC if that helps. I believe, but not too sure, RoboPDF
is still on my PC. May this have something to do with it?
Thanks so much, in advance, for any feedback and help.

Try generating just to Word and then creating the PDF from
there. There is a known problem which affects some users but not
others. Cause not known.

Application Error while generating printed documentation

I have Rh 10 installed in my 64-bit machine with Windows 7 OS.
The problem is when I click Printed Documentation and click Next in the Printed Documentation screen, Rh crashes.
Without clicking Next, if I click Save & Generate, pdf is generated with missing topics.
When I check the event log, I see Application Error. What exactly is causing this crash? Please help.

Which version of Word do you have installed and is it the 32 or 64 bit version?
The latter will not play nicely and even Microsoft recommend the 32 bit version for compatability with other apps.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Missing Index Entries in Printed Documentation

Similar Messages

Maybe you are looking for