2017 Release of RoboHelp (Update 1)

We are constantly working to make Adobe RoboHelp better for you. In this Update we have included a number of improvements and fixes to make RoboHelp even better for you and the users of the content you produce with RoboHelp.

Please continue to send us your feedback, we’re listening!

In this post:

What’s new and better

Following the list of enhancements and issues fixed in Update 1 for Adobe RoboHelp (2017 release). The complete list is also available here.

  1. We improved dynamic content filters: Now a topic’s index entries are also hidden when the topic is set to hidden. Makes it less confusing for your readers.
  2. In some scenarios, a blank TOC was displayed in the new Responsive HTML5 Indigo layout in Apples’s Safari browser. We fixed that.
  3. And another fix for Indigo on Safari (MacOS Sierra): Sometimes the scrollbars were not shown. Fixed.
  4. In the Indigo layout the Dynamic Content Filter panel shows a title now which makes it more clear.
  5. In the Indigo layout, the title of the add/remove favorite button now changes properly.
  6. You spent a lot of time customizing your personal Ocean layout? Those customizations will work as expected now.
  7. When Show Default Topic option in the Ocean layout is turned off, the topic is displayed now when a link is clicked from the TOC.
  8. In the Ocean layout, SVG image preview is supported now also for the Banner tab.
  9. You are linking FrameMaker (2017 release) files in your RoboHelp project? In the first 2017 release of RoboHelp you had to have FrameMaker running (open) on your machine to import FrameMaker files. This is no longer necessary now and FrameMaker automatically starts for the import.
  10. When the responsive HTML5 output is hosted on RoboHelp Server 10, the TOC and Search load properly now.
  11. The Starter Screen in the the localized versions of RoboHelp displays the correct RoboHelp version number now.
  12. You have a complex CSS system with multiple CSS files linked into each other? You will love to hear that this works now.
  13. Gone is the “Scripting error” in Internet Explorer 11 when you click the “Show output in full context” link.
  14. We fixed a couple of scripting errors while opening multi-screen HTML5 outputs.
  15. You think, the sample projects shipped with RoboHelp should be just perfect? We think so, too. And fixed a few glitches. Update 1 fixes the sample projects in Program Files. You can copy these sample projects in C:\Program Files (x86)\Adobe\Adobe RoboHelp 2017\RoboHTML\Samples and save them in My RoboHelp Projects in your Documents folder. Rename the earlier versions if you want to keep them for some reason. (Thanks, Peter Grainge for your note here!)
  16. Now large image pop-up no longer appear for images that are marked as zoom-able.
  17. Export to DocBook: We fixed that nasty error that appeared while exporting a project or topic to DocBook.
  18. Working with RoboHelp Screen Capture? Seeing it launching it from RoboHelp is real pleasure now again.
  19. There was a particular case, when generating a Mobile App output throwed a runtime error. And no one likes runtime errors, right? Fixed!

You can also download the RoboHelp (2017 release) Update 1 Readme PDF here.

How to get Update 1 for RoboHelp (2017 release)

Getting the update is as easy. Just select File > Help > Updates from RoboHelp’s main menu to fire up the Adobe Update Manager (AUM) to download and install the update.

Want to download the update to deploy it to all your RoboHelp installations without downloading it on every machine? We understand this. That’s why you can find all update packages for download also on our Adobe RoboHelp Service Releases website.

After the update, the RoboHelp version will be 13.0.1.279. That’s good to know, isn’t it?

Found a bug? Want to suggest an improvement? Let us know!

You found a bug? You have an idea? You want to get something improved in the product?

There’s a channel for that: We call it “Adobe Tracker.” Adobe Tracker is your place to go, when you find a bug and want to report it to us, so that we can fix it in the next release. You can also file in your feature requests, ideas, requests for improvements. It’s very esy to do and the reports go directly into our systems, and our product managers, engineers and support people have direct access to it.

Before you file in a bug report or idea, you might want to check, if someone else has done it already. You can search through the database here. In case you find something fitting, you can add comments to the existing bug and you can also “vote” for this bug or feature request. And the more people vote for a feature … You get the idea.