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? 

Similar Messages

  • Missing Topics in Printed Doc

    I am losing my mind! I am trying to generate printed doc for
    the sole purpose of sorting a bunch of pages in hard copy to
    rethink the organization of one part of my projects. Ironically,
    every time I generate the printed doc (i've done it about 20 times
    so far), these pages are nowhere to be found! I've included them in
    the TOC, I've moved them out of a book within a book, I've deleted
    them from the TOC and added them to a book that is generated as a
    chapter. I've renamed the book to remove non-alpha characters. I've
    deleted the book and created a new book with a completely unrelated
    name. NOTHING I do will get these pages to print. SO - I have 175
    pp. document of the 175 pages that DONT need to be printed and I
    can't for the life of me print the +/-20 pages that are the ones I
    want in hard copy.

    first, I am using RH version X5.0.2.
    1. On your Project tab, all the way at the bottom, open the
    Single Source Layouts directory. Double click on Printed
    Documentation.
    2. Set up your doc name, path, and build expression as
    needed. Click on Next.
    3. This next window is where you can select any or all topics
    to include in the printed doc. It defaults, I believe, to all
    topics and chapters. Just select each chapter or topic you do not
    want and click on the left-pointing arrows to move these topics out
    of the list on the right side of the window. Only the topics and
    chapters listed in the right side (under chapter layout) will
    print. This selection window works much like the Browse Sequencer
    tool.
    4. When all appropriate topics are excluded / included, click
    on Next. In this window, you are establishing the sections of the
    resulting doc - set up sections as needed. If you aren't publishing
    this doc for distribution (just for yourself), I wouldn't worry too
    much about this step. Click on Next.
    5. The last step before the doc generates is to determine
    which Styles set you will use - the styles you use in RH, or a Word
    Style set. Again, since this is just for you, don't sweat it. I
    just use the Project's CSS Styles (select this option from the menu
    at the top of the window).
    6. Click on Finish, let 'er rip, and see what comes out.

  • 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.

  • Printed Documentation displays each topic twice

    Click Printed Documentation.
    Click Next to access the TOC setup
    On the right panel, each topic is listed twice. In the final document, RH is adding a heading to a topic and then duplicating the same topic without the RH heading.
    If there is a way to prevent RH from inserting these headings, I think this duplication would be resolved.

    That's what I was getting at earlier in the conversation but I don't think that is the cause here.
    It use to be that if a topic was linked to a book and then the author added the topic because it could not be seen in the print layout, the topic would be in the printed document twice. In the print layout you had to remove the topic and rely on it coming from the book, which it did. In the print layout you would not see the topic whereas you are seeing it twice.
    In Rh10 there is a change (may have been in 9). In the print layout if there is a book with a linked topic, that now shows in the print layout. Rh has put the linked topic in the layout so that you can now see it. However, it is only there once.
    I am wondering if maybe you had books with links and had put the topic below not realising, then on upgrade you would see your manually added topic plus the one Rh has moved from the book to the print layout? Can you look at an old document to see if the topic was there twice?
    Beyond that I don't know what could have caused it but all seems well now.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • FluxBB missing option to print a topic?

    Hi,
    The IPB && vBulletin boards have an option to view the topic in print mode and display all of the quote, code boxes' contents.. I'm trying to print a topic to file:
    https://bbs.archlinux.org/viewtopic.php?id=78454
    and when using just the browser's print option, the boxes do not display all of the text.
    Any help?
    Edit:
    Last edited by nimd4 (2012-10-07 23:43:41)

    It's hackish, but you can remove the stylesheets. I'm using
    javascript:(function(){var%20i,x;for(i=0;x=document.styleSheets[i];++i)x.disabled=true;})();
    as a Firefox bookmarklet.
    Readability plugins (a more sophisticated version of the above js function) are another way.

  • 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 topics in pdf-document

    Hello,
    I am using RH 7 and creating WebHelp. I am also trying to create a pdf-document with the same content as the WebHelp. For some reason, the contents I specify for the pdf-document are only partly included in the pdf-document.
    I use the TOC from the project where I have a some books without links (all the associated topics are included in the pdf-document all right), and one book with a link - these topics are not incuded in the pdf. All topics are included in the WebHelp without any problems.
    So I am wondering if there is something that could prevent a topic from being included in a pdf-document? Does anybody know? And last, but not least, does anybody know how to solve this problem? I have compared the topics that are inclucded in the pdf with the ones that aren't, but I can't see any difference.
    Thanks in advance for your reply!
    Regards, Hanne
    P.S. I have been through Printed Output on www.grainge.org without being able to find a solution.

    Hi Peter,
    Thanks for your suggestions, I am afraid I have not found a solution yet. Outputting to Word gave the same problem.
    The TOC in the output is in fact different from the TOC in the TOC editor in the sense that missing topics are missing from both the TOC and the "body"  of the output. Sorry if I did not make that clear in my first post.
    I have a feeling that I must be doing somthing wrong in the Chapter Layout part of the wizard for printed documentation. I have tried creating the books from scratch (by creating and renamingnthem) to see if that would help but it did not. My topics are not imported from Word; they have, however, at some point been imported as htm-files from another project as far as I remember.
    The real mystery about it is that my pdf output worked all right in an earlier version of the project. My current project is a copy of that project. I am not aware of having changed anything in the pdf settings, and they look exactly the same (I have compared the settings field by field).
    Do you have any suggestions for a way of "resetting" all pdf settings, or should I perhaps try to import the .hhc file from my previous project where they pdf is correct?
    Thanks in advance!
    Regards, Hanne

  • Missing Topics in Topics box

    As you can see there is a lot of missing subtopics under the Main Menu Overview topic in the left hand Topics Box. These topics all show up in the ,.chm file. Can anyone tell me how to correct this. I can't add the missing topics to the printed doc. If they do not show up in the Topics Box.
    I am using RoboHelp HTML version 7.03
    Lee

    Hi Lee
    Sorry, the site belongs to fellow Adobe Community Expert Peter Grainge, not me.
    Secondly, I think what Peter points out in the page I linked to was that the first time you create Printed Documentation and move through the dialogs, the TOC used *AT THAT TIME* determines the topics. So if you come back later after having added additional topics to the project, you need to take some special steps in order to see those topics reflected in the dialog. That was my thought as to why you weren't seeing them.
    I suppose a valid test here would be to right-click the Single Source Layouts pod and create a fresh layout for Printed Documentation. If you try that, do the topics finally appear?
    Additionally, do you have more than one TOC defined for the project? If so, have you ensured you pointed to the correct or desired TOC?
    Cheers... Rick
    Helpful and Handy Links
    Begin learning Captivate 5 moments from now! $29.95
    Captivate Wish Form/Bug Reporting Form
    Adobe Certified Captivate Training
    SorcererStone Blog
    Captivate eBooks

  • RH10 - Printed Documentation Issues.

    Hi!
    I'm new to RH10. I've started a new Technical Authoring role having taken 6 years out of the role... In my previous roles I've walked into the company and the styles and templeate were already set up and I just got on with the authoring part of the role. However, this time I'm starting from scratch, so am requiring some help.
    I've used Robohelp in the past and decided this was the software to go along with. However, it's quite a bit different to how I remember it!
    Currently I am using a trial of Robohelp 10. I have created a test project and managed to generate a Microsoft HTML Help file. I'm now trying to generate this into a printed document. Issues I'm having are:
    Firstly I seem to have a line of text which is set as Conditional Build Tag of Online only showing in my printed document. There are other Onliine only bits that are not showing, but this particular line I just cannot seem to remove from the printed document. Any suggestions on how to deal with this? I have removed the conditional tag and re added it.
    The company's brand is to use Tahoma font. However, I'm finding that when I print the document it comes out in grey, even though I've set the font colour to be automatic. I've even tried to swap this to being black, but I still seem to get grey print. Is this down to the font type I'm using or could there be an issue with the generation?
    I've set my Heading 1 style to be centred for the title page and still it prints out left alligned. Am I missing something with the style?
    Finally, each of my topics are coming out printed on a new page, even though I have not selected the 'Start each topic on new page' check box when setting up the generation options. Can you point me in the right direction to adjust this please.
    I'm sure that mose of these are user error and probably down to my rusty authoring. But hoping that help on these will help me to move forward and loosen up the rustyness!!!
    I look forward to hearing from you soon.

    Online Conditional Build Tag: You may want to check what Conditional Build Tag expression is being used in the Printed Documentation single source layout? This controls the content that is included. However be aware that content in a topic (or a topic itself) can have more than one tag assigned to it. I think this will be a case of going back to the topics that have the online tag and doing some investigation. You can easily identify the topics with a CBT by right clicking on a tag in the Conditional Build Tag pod and selecting Properties.
    This could be down to the Word styles you are using in the template and how they are mapped to the RH Styles. Check out the following link for an excellent tutorial on producing printed documentation. http://www.grainge.org/pages/authoring/printing/printing.htm
    See point 2.
    Again this is style related. It sounds like you have a Word style mapped with the pagination option selected. See point 2.

  • Cannot explain missing topics?

    In DOC/PDF ouput generated with 'Printed Documentation' wizard 2 topics are missing. I'm NOT using any conditional build tags here, and the topics are also included in topics dialog in 'Printed Documentation' wizard (2nd dialog in the wizard).
    I have removed and re-added both topics, but this doesn't change a thing.
    I only discovered this when creating a new single source layout for printed ouput from scratch, using the exact same settings as in above 'Printed Documentation' layout.
    Maybe a file is corrupt or so? Any suggestions.
    Best regards,
    Herman

    I now know why the topics were missing.
    I checked the 'Output View' log and found following error:
    Missing topic '!SSL!\Printed_Documentation\!doc_tmp_folder_0\Special_matters\Valuation_of_inventory_wit h_standard_cost_price_system\D._Valuation_of_inventory_with_standard_cost_price_system.htm '.
    Failed to process 'D. Valuation of inventory with standard cost price system'...
    After some trial and error, it turns out that the output file path is too long (my guess is that the length is limited to 256 characters) .
    When updating this filepath in the layout created from scratch that worked OK, the topics also were not included.
    Kind of sloppy.
    Best regards,
    Herman

  • Unable to generate printed documentation

    I am running RoboHelp 9 HTML using Microsoft Word 2010 on a Windows 7 machine.
    Whenever I try to generate printed documentation using a single source layout that is set up for generating either a .docx file or a .doc file the program hangs up after printing the output message "Processing Topics". This occurs with the simple "Test" sample provided by Adobe that contains only one topic as well as with a more complicated project.
    I read some posts that said things about anti-virus software that may affect RoboHelp. On my system the security department at my company has control of that, so I am not really sure what anti-virus software I have. When I look in my "All Programs" list under the "Start" menu, I do not see any anti-virus software programs except something called "System Center 2012 Endpoint Protection". I believe this is the anti-virus software that the security department uses, and there is an icon for it in my System Tray. Has anyone ever heard of issues involving that software and RoboHelp?
    Meanwhile any other insights any of you may have into this problem would be greatly appreciated.

    Are you generating to a local drive or a network drive? If the latter, try the former.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Footer image not resizing in printed documentation

    RH11
    Does anyone know why an image inserted into a footer master page is not automatically resizing to the width of the printed page when applied to a print layout and output to Word? If you insert an image into the body of a topic or a master page and generate printed documentation, the image automatically resizes.
    I'm trying to insert a high-res footer image (300 dpi) into my footer so that it appears on every page, but at the moment it's being embedded at full-size.
    Thanks
    Jonathan

    Firstly, your better off using liststyles than paragraph list styles, I screwed around a long time before I had to set everything to liststyles rather than paragraph ones. So dont worry about that.
    The first issue, of not seeing the style - it is there, if you open the Styles tab on screen (click in a topic to get the cursor, then Format > Styles), not just the dropdown like youve shown youll see a list of all your styles, almost, it will show paragraph styles, click the drop-down and select All available styles, this will display your list styles as well!
    Im not sure about the style settings, I have the same text setting applied in my list style as I use for my 'normal' text. Though I think you can select the text in a list and apply a paragraph style to it....i just tried and it worked, but to be on the safe side you might want to set the text formatting in the list style css too..
    mine looks like this
    li.NumberList {
        font-family: Helvetica, sans-serif;
        font-size: 10pt;
        color: #524C45;
        list-style: decimal;
        margin-bottom: 6pt;
        margin-top: 6pt;
    As for printed formats not indenting lists, this is an issue. So far I have found no way around it because you cannot map a  list styles in RH to a list style in Word. This has also created errors for line spacing and indents - and  I found the indents are severly messed up when using list styles in snippets. Everytime I create printed documentation I have to manually fix it, a pain but it doesnt take too long....you could use macros etc to speed it all up for you.
    Submit a Wish Form.
    Hope it helps.
    Nick

  • Missing topic in PDF

    Hi,
    I am using RH 9.
    I have converted content created in RH 6 or 7 (not sure)
    I have added a topic, it is in the TOC, and generated web output
    I need to create a PDF.  The new topic does NOT appear in the in the PDF TOC or in the body of the PDF
    Is there a fix for this?

    When you use the Printed Documentation single source layout to create the PDF, the second step allows you to select the topic that will be included. You'll probably had the TOC filter set by default. If you change this to a folder, you'll be able to select the topic that isn't in the TOC and add it to the output.
    BTW you may find it easier to create a Word file first and then PDF that.
      The RoboColum(n)
      @robocolumn
      Colum McAndrew

  • Missing pages in printed document

    Some topics are missing in the printed document. What could be the reason for this? I have tried and tried but could not get those pages printed.

    Welcome to the RH forums.
    Perhaps you could give us some additional information which would help us here. What version of RH are you using? Is the problem only in one project or on one PC? Is it the same pages that are always missing? Are they always missing from the start, middle, end? That sort of thing.
    For a start, check that you have included all the required pages correctly. Check out this link.  Also check to see if you have any Conditional Build Tags that could be filtering out the topics you are expecting to see.
      The RoboColum(n)
      @robocolumn
      Colum McAndrew

  • 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:
    <!--(Title)=========================================================-->
    Replace With:
    nothing
    Search for:
    <!--(See Also)======================================================-->
    Replace With:
    nothing
    Search for:
    <!--(Content)=======================================================-->
    Replace With:
    nothing
    Search for:
    <p> </p>
    Replace With:
    nothing
    Search for:
    <p> </p>
    Replace With:
    nothing
    Search for:
    <html>
    <head>
    Replace With:
    <html>
    <!--(==============================================================)-->
    <!--(Document created with RoboEditor. )============================-->
    <!--(==============================================================)-->
    <head>
    Search for:
    <!--(Meta)==========================================================-->
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    <!--(Links)=========================================================-->
    <link href="MyHelp.css" rel="stylesheet" type="text/css">
    <!--(Scripts)=======================================================-->
    <script language="javaScript" type="text/javascript" src="MyHelp.js"></script>
    <script language="javascript" src="eHlpDhtm.js"></script>
    </head>
    <!--(Body)==========================================================-->
    <body TABINDEX=1>
    Replace With:
    <!--(Meta)==========================================================-->
    <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>
    <!--(Links)=========================================================-->
    <link href="MyHelp.css" rel="stylesheet" type="text/css">
    <!--(Scripts)=======================================================-->
    <script language=javaScript
      type="text/javascript"
      src="MyHelp.js"></script>
    <script language=javascript
      src="eHlpDhtm.js"></script>
    </head>
    <!--(Body)==========================================================-->
    <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!

Maybe you are looking for

  • Recording a Voice Over w Kona3 xlr in FCP 6

    hello all i've got a fcp 6 setup with a kona 3 card and want to record Voice Overs straight into the timeline but am having some difficulties getting any results. The system is brand new and the card is installed properly but i'm not sure what i need

  • How to read variable in CMOD code !

    Experts, in my one of the query, there is a variable, which takes 2 dates. so the variable is type "interval" so, when you run the report, user needs to enter value something like this.."mm/dd/yyyy  - mm/dd/yyyy" Now, i have writtn a code in CMOD, by

  • About executing a executable program in background

    Hi to all I created a report program having one variant and downloading its content in a flat file using ws_download function. When I am going to download this in background , i am not getting the result. I am fulfulling all requirement to schedule a

  • Finding an object's "path"

    Hello, I'm trying to write a plug-in for Flash CS5 that will display the "instances path" for a selected object. I'm trying to work with JSFL. I manged to get all selected objects using fl.getDocumentDOM().selection. I iterate over the array I get an

  • How to delete and start again?

    I've finished ripping my collection of 480+ CDs but I really think a big mistake I made was signing-up to Match before I'd finished. I've got various minor problems (such as mismatched art which won't synchronize) and some bigger problems (such as so