EDIT: Peter and Adobe are now aware of these issues, and I'm working with them to find a solution. If anyone else experiences the problems I've found, they're working on it. Any updates or workarounds will be posted at the end of this thread. I have tried to generate Word output from the RoboHelp Reimagined project, but the result has multiple issues. These issues concern both the use of a CSS to generate the word styles, as well the use of a Word template to map the Word styles to. I have created a test project, where I start off by creating Word output by CSS only, and then step by step use a Word template to map the styles, style by style. I have added a lot of screenshots to show which settings are used, and what the result looks like in Word and which styling is used. You can find this project and its description here:https://drive.google.com/drive/folders/109ytnkuZEcXCvrVYbHmu87TLnVLsQmvk Summary:When generating from CSS, RH also adds Heading1, Heading2, etc. and uses those styles, instead of the built-in Heading 1 etc. styles, which is confusing. Moreover, it still applies direct formatting to its own created Heading2 style to make it look like the CSS style.When generating with a template, and mapping styles, RH looks at the styles to see how the text should look, but then creates that look not by using the styles themselves but makes everything Normal + direct formatting.So while the generated Word document may look somwehat like the template, under the hood the styles are one big mess. The whole reason for generating in Word instead of PDF is to gain control, but if every style becomes Normal except the headings, there is almost no control whatsoever. Since they just added Word output, I'm not surprised it's still a bit buggy. But I hope they solve these issues in the near future.

Please ignore this specific post and see further on. I believe the cause of the problems has been resolved as detailed in later post. It has worked for me and I have asked Erwin to try it as well. I have been working on this with Erwin and I have raised the issues with Adobe. I had hoped to be given a bit more time to let them respond. I have worked on the RoboHelp Reimagined sample project and found what I think is the root cause and a workaround pending resolution. THE CAUSEThe Word template path has been removed here but a template was used and it had the Word styles in it. However as you can see Map to Style is not seeing it. What then happens then is RoboHelp creates Heading1 (rather than using Heading 1 - note the space) so you get Heading1 as a name but it is based on Normal so the font and the background are inline. THE WORKAROUNDGenerate the document and open it in Word.Open the Styles pane.Go to the first instance of Heading1 as created by RoboHelp.Select the line.Locate Word's own Heading 1 which will be further down the list of styles.Right click the style name and click Update Style to Match Selection. That will do two things. It will make Word's Heading 1 be in line with the document created and it will apply that style to all instances.At the bottom of the styles pod click Manage Styles and delete the Heading1 created by RoboHelp.Repeat for any other affected styles.At this point you can now modify the styles to whatever you want. The easiest way of doing that is to go Manage Styles again and click Import/Export and import the styles from a document that does have the required styles in. I realise this is extra work but it will help if you must work this way. Personally for now I would take my topic CSS and create a copy of it and amend the styles there. Then I would apply that CSS to a master page and select that. It will not get around the problem of RoboHelp creating Heading1 etc but it will instantly give you the required output. As I indicated I have reported this to Adobe and will update this thread when I hear back.www.grainge.org

Erwin.Timmerman

Inspiring

Question

RH2019.0.9 New UI - Word output issues

Forum|Forum|6 years ago
November 27, 2019
11 replies
728 views

EDIT: Peter and Adobe are now aware of these issues, and I'm working with them to find a solution. If anyone else experiences the problems I've found, they're working on it. Any updates or workarounds will be posted at the end of this thread.

I have tried to generate Word output from the RoboHelp Reimagined project, but the result has multiple issues.

These issues concern both the use of a CSS to generate the word styles, as well the use of a Word template to map the Word styles to.

I have created a test project, where I start off by creating Word output by CSS only, and then step by step use a Word template to map the styles, style by style. I have added a lot of screenshots to show which settings are used, and what the result looks like in Word and which styling is used. You can find this project and its description here:

https://drive.google.com/drive/folders/109ytnkuZEcXCvrVYbHmu87TLnVLsQmvk

Summary:

When generating from CSS, RH also adds Heading1, Heading2, etc. and uses those styles, instead of the built-in Heading 1 etc. styles, which is confusing. Moreover, it still applies direct formatting to its own created Heading2 style to make it look like the CSS style.
When generating with a template, and mapping styles, RH looks at the styles to see how the text should look, but then creates that look not by using the styles themselves but makes everything Normal + direct formatting.
So while the generated Word document may look somwehat like the template, under the hood the styles are one big mess.

The whole reason for generating in Word instead of PDF is to gain control, but if every style becomes Normal except the headings, there is almost no control whatsoever.

Since they just added Word output, I'm not surprised it's still a bit buggy. But I hope they solve these issues in the near future.

This topic has been closed for replies.

Show previous replies

Peter Grainge

Community Expert

Please ignore this specific post and see further on. I believe the cause of the problems has been resolved as detailed in later post. It has worked for me and I have asked Erwin to try it as well.

I have been working on this with Erwin and I have raised the issues with Adobe. I had hoped to be given a bit more time to let them respond.

I have worked on the RoboHelp Reimagined sample project and found what I think is the root cause and a workaround pending resolution.

THE CAUSE

The Word template path has been removed here but a template was used and it had the Word styles in it. However as you can see Map to Style is not seeing it.

What then happens then is RoboHelp creates Heading1 (rather than using Heading 1 - note the space) so you get Heading1 as a name but it is based on Normal so the font and the background are inline.

THE WORKAROUND

Generate the document and open it in Word.

Open the Styles pane.
Go to the first instance of Heading1 as created by RoboHelp.
Select the line.
Locate Word's own Heading 1 which will be further down the list of styles.
Right click the style name and click Update Style to Match Selection. That will do two things. It will make Word's Heading 1 be in line with the document created and it will apply that style to all instances.
At the bottom of the styles pod click Manage Styles and delete the Heading1 created by RoboHelp.
Repeat for any other affected styles.
At this point you can now modify the styles to whatever you want. The easiest way of doing that is to go Manage Styles again and click Import/Export and import the styles from a document that does have the required styles in.

I realise this is extra work but it will help if you must work this way. Personally for now I would take my topic CSS and create a copy of it and amend the styles there. Then I would apply that CSS to a master page and select that. It will not get around the problem of RoboHelp creating Heading1 etc but it will instantly give you the required output.

As I indicated I have reported this to Adobe and will update this thread when I hear back.

www.grainge.org

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded