RoboHelp 9.0.2 is now available!!

Thursday, December 15 2011 @ 12:17 PM, By Ankur Jain

Dear RoboHelp Users,

I’m pleased to announce the availability of Adobe RoboHelp 9.0.2 Service Update. As part of this service update, we have fixed several issues that were reported to us by our users and valued partners. In addition, there are some enhancements in this service update as well. Here is a summary of the fixes/enhancements in this service update:

ePub Output:

  1. We have moved to a different file archiver to resolve some of the validation errors in the ePub output. This will be especially useful for those who are looking to publish eBooks to Apple bookstore etc.
  2. MOV and MP4 files were not supported in the ePub output. RoboHelp 9.0.2 service update allows you to have MOV and MP4 files in your ePub output that you will especially find useful on iOS.
  3. The Cover Page behavior in the ePub output has been enhanced. The Cover Page image will now appear while viewing the ePub output in Adobe Digital Editions.

After installing the update, please copy the updated ‘ePub Generator.jsx’ script from [InstallDir]/RoboHTML/presets/scripts/ to the following location:
                  On Windows XP: [USER]/Application Data/Adobe/RoboHTML/9.00/Scripts/Sample Scripts/
                  On Windows 7: [USER]/AppData/Roaming/Adobe/RoboHTML/9.00/Scripts/Sample Scripts/

Merged CHM Output:

  1. In some cases, generating merged CHM output of upgraded legacy projects used to fail. This has been fixed now.
  2. The HHP file was always overridden while generating CHM output. This has been fixed now

If CHM merging doesn’t seem to work after applying RoboHelp 9.0.2 service update, please follow these (one-time) steps:

  • Remove all merged TOC links from the parent project and create fresh links. Save the project and regenerate.
  • Ensure that all merged child projects are listed under the MERGE FILES section of the .hhp file present in the parent project before regeneration.

Import/Link Microsoft Word and/or Adobe FrameMaker Content:

  1. Some options present in the Other Settings section of the Conversion Settings dialogue were not being saved in a few cases when importing a Word document into RoboHelp. These settings will now be honored.
  2. PNG images embedded in Word documents used to lose quality when imported into RoboHelp. The PNG support has been enhanced now. Please enable Allow PNG as a graphics format setting in Microsoft Word to take advantage of this enhancement in RoboHelp.
  3. When importing documents from Word, table and cell width values were being lost in case you have mapped the Table style. This has been fixed now.
  4. Style names were not getting preserved when importing Word documents into RoboHelp. This has been fixed.
  5. Incorrect paragraph style was getting generated in the html code when mapping the Normal style from Word to the Normal style in RoboHelp. This has been fixed.
  6. The CSS defined for style mapping was not being applied on paginated topics for linked Word documents. This has been fixed now.
  7. Importing Word documents with sections used to bring in extraneous DIV code in topics. This has been fixed now.
  8. In the Conversion Settings dialog box, the Pagination label did not reflect that the option is to be used to split the document into topics based on a selected style. The new label makes it clear.
  9. FLV format in imported or linked FrameMaker documents was not getting preserved. This has been fixed now.
  10. If the Use Underscores in File Names option is selected and topics in linked FrameMaker documents have cross-references, the topic titles were getting prefixed with an underscore. This behavior has been fixed now.

Adobe Captivate 5.5 Users:

  1. Captivate 5.5 was launched after RoboHelp 9. This update allows you to use Edit with Captivate option with Captivate 5.5. If you have Technical Communication Suite 3.5, then you have this fix already.

Printed Documentation Output:

  1. The PDF settings were not enabled in the Printed Documentation SSL in certain scenarios related to Word 2010 and/or PDF Add On. This has been fixed/enhanced.

RoboHelp for Word Users:

  1. Some of you reported that RoboHelp for Word fails to import Microsoft Word documents if Microsoft Word 2010 is used with it. This service update should fix that problem.

RoboSource Control Users:

  1. For a fix to the problem of being unable to check in files with RoboSource Control, on a 64-bit system, see the article Can’t check in files.

RoboHelp 9.0.2 update is now available through Adobe Update Manager (AUM). You can check for updates through Help>Update menu in RoboHelp 9. It will be available for download from RoboHelp Support Center later today. I encourage all the RoboHelp 9 users to install this update.

I would like to take this opportunity to thank all those who contributed by reporting these issues. Special thanks to Peter Grainge, Kevin Siegel, John Daigle, Rick Stone, and Matt Sullivan for their valuable contributions.

Hope you find these fixes and enhancements useful.

Ankur Jain
Product Manager – Technical Communication Suite | RoboHelp | RoboHelp Server
Follow me on Twitter: @ankurjain8

COMMENTS

  • By Wendy Ewing - 5:56 PM on January 6, 2012  

    Do I need Robohelp 9.0 to install this update as to I have 8.0?

    thanks

    • By Ankur Jain - 6:52 PM on January 6, 2012  

      Hi Wendy,

      This service update is for RoboHelp 9 users, so you need to have RoboHelp 9 to be able to apply this update.

      Thanks,
      Ankur

  • By Thomas Rankin - 1:04 AM on January 18, 2012  

    Hi,

    I have RoboHelp 9.0.0.228, but I’m not sure how to obtain the Service Update. Could you give me instructions?

    Thanks and regards,
    Tom

  • By Thomas Rankin - 7:30 PM on January 19, 2012  

    Thank you, Ankur. I downloaded the Service Update and it went fine.

    Regards,
    Tom

    • By Ankur Jain - 6:44 AM on January 20, 2012  

      Great.

  • By Cathy Nelson - 10:02 PM on January 31, 2012  

    I downloaded the service update and now no matter which RoboHelp project I open, it crashes. The 9.0.1 version did not have this problem.

    • By Ankur Jain - 5:22 AM on February 2, 2012  

      Cathy, thanks for sharing this. Someone from the Adobe team will be in touch with you shortly to investigate what is causing this crash problem on your machine and get it resolved.

  • By Neelima Mehta - 9:53 AM on May 16, 2012  

    I updated service release 9.0.2 on my machine. Post this update, robohelp stopped working on my machine. It requests to re-installation of the product. (See the attached image for error details.)

    • By Ankur Jain - 6:09 AM on July 3, 2012  

      Neelima, that’s strange. I haven’t heard this from anyone else so I’m guessing it may have something to do with your set-up. Please contact Adobe Customer Support and they should be able to help you.

  • By Barb - 3:33 PM on June 28, 2012  

    Have uninstalled, reinstalled, and applied patch 9.0.2 multiple times with the same result: RoboHelp 9 for Word refuses to list Word 2010 in the default word version. Upon opening an older RoboHelp for Word file, I receive the following error message:

    Compile error in hidden module: AutoOpen

    Clicking the “Help” button does no good. The error message being displayed is a Microsoft Visual Basic for Applications error message. I have checked the Roaming/Microsoft/Templates directory and have Normal.dot and Normal.dotm; I have all the RoboHelp .dot files but I have no .dotx files anywhere.

    I am able to open, modify, and save the older help project in RoboHelp for HTML, but changing the document as an HTML file is not an option.

    I have followed all the tips and checkpoints as discussed on the Adobe help for RoboHelp forum but nothing has made a difference.

    I need help or I need different help authoring software.

    • By Ankur Jain - 6:15 AM on July 3, 2012  

      Barb, someone from the Adobe Customer Support team will reach out to you and help you on this.

      Ankur

  • Categories

  • Archives

  • Authors

  • Useful Links

  • Recent Comments

    • Joel: Thanks for fixing the links guys!
    • Maxwell Hoffmann: Ted, one aspect of the blog that may have escaped your notice; you can launch the HTML5 version in...
    • Maxwell Hoffmann: Joel, per comments made above, I discovered that the original URLs were incorrect with pointers to...
    • Maxwell Hoffmann: Paul, as I indicated in the comments below, the original blog had links that pointed to a...
    • Maxwell Hoffmann: I apologize to all concerned regarding my suggestion to “clear the cache” … it...