RoboHelp 2019 Classic Does Not Include Parentheses Text in Responsive HTML5 Output

Forum|Forum|6 years ago
October 24, 2019
7 replies
752 views

When I output my RH 2019 classic project into responsive HTML5 help, any parentheses I use are not generated in the output.

For emample, in my project I write "Close Time (sec)." The HTML5 output renders the text as "Close Time sec" without the much needed parentheses. This issue occurs throughout the project.

Does anyone know what could be causing this issue? It's small and somewhat bizarre, but as a technical writer, I obviously need to use parentheses.

This topic has been closed for replies.

Correct answer Peter Grainge

See RoboHelp 2019 on my site. It's a known issue and there is a link to Adobe's fix.

www.grainge.org

Peter Grainge

Community Expert

Yes the search issue will be fixed in an update.

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

Peter Grainge

Community Expert

It's not an issue in 2019.0.9 topics except in a search.

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

Erwin.Timmerman

Inspiring

Ah OK, indeed I was looking at the topic via a search. Via the TOC it indeed displays correctly. Do you know if they will be working on this as well? I think more people will look at topics by using search than by using the TOC.

C

clayton1994Author

Known Participant

I am not sure about the sample project, but the issue does occur in my other projects as well.

Peter Grainge

Correct answer

Community Expert

See RoboHelp 2019 on my site. It's a known issue and there is a link to Adobe's fix.

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.

Erwin.Timmerman

Inspiring

Hi Peter,

I've got the same problem on the new RH interface, in 2019.0.9 (or 14.0.9 as the Adobe updater calls it). Your site says that update 9 fixes this issue for the classic interface, but for the new interface that is apparently not the case?