We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
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:
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 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.
Generate the document and open it in Word.
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.
This only explains the first bullet point, not the second, which is much more important IMO.
If you read the description I've put in the link, you'll see that when using a template Heading1 etc. don't give an issue at all, because they are mapped. But all the other styles that RH does recognize aren't used, but they are recreated via Normal + direct formatting. See the EmphasisOne style. That completely defies the use of styles.
You've only taken up the first issue with Adobe, but not the second. If they only fix that, they're not even halfway there. My sample project and description show in great detail what goes wrong when mapping styles, I hope they can use it to fix things. I can't copy/paste all of it here, because there are too many screen shots showing what happens to include them in this post.
Word can only have the supplied Heading styles, you cannot create new Heading styles. Thus the Heading1 that RoboHelp creates is Normal plus formatting. The workaround I have given fixes that by converting all instances of a style to the correct Word Heading styles. Word's Heading 1 becomes correct and replaces the old Heading1 which is Normal + formatting. Also I have made Adobe aware of that.
I have also just gone through your project and the document and replied direct to you.
It is making it very difficult when you are posting to both the forum and direct and not allowing me some time to get back to you.
The reason the mapping was not working is because while the template contained the styles required, there is also a requirement to actually use them in the template.
By adding some text to the template and applying the styles, on generating the document Heading 1 mapped to Heading 1 in Word without any inline styling. Hopefully Erwin will confirm the same result.
I am grateful to the Adobe developer who resolved this at about 9pm!
This indeed works for the headings, but for some reason not for the other paragraph styles, at least in my setup. These are still created as Normal + inline styling.
However, I'm working with Peter to resolve these issues, and Peter as well as Adobe are now aware of the extent of the problems. So if anyone else experiences the same, they're on it!
That's great! One other thing I found though: if my project contains svg images, these go missing from the Word file. PDF output works just fine with the same svg images.
Anyone else tried this and succeeded/failed? Can I add that to this thread or is it better to make a separate thread for this?
I just tested and got the same as you. For now the workaround would be to have both SVG and PNG or whatever and use tags.
I suggest the issue is reported as a bug. Please follow this link to report bugs or request features. https://tracker.adobe.com
Post the link to your bug report / feature request in this thread and others can vote for it. The more people who do so, the higher it gets prioritised.
There's no real need to start another thread as it's flagged here but it may make it easier for others finding the same issue to search for it. If you do, then obviously post the bug link there.