RoboHelp adding an extra backslash in TOC (.hhc) in generated HTML5 Output

[SGRoeh]

I searched the Forum but could not find anything related to this...

My problem/issue/annoyance is that, in the TOC of one of my RH2017 projects, I have a backslash:

When I generate the HTML5 output, RH adds a second backslash for some reason:

The TOC link in the generated output works and the topic itself looks fine:

I did a NotePad++ search in the folder of where the generated output is published to and found these instances of where these double backslashes occur:

Again, everything seems to work fine, I'm just wondering if anyone else has come across this issue/annoyance and if there's a way to prevent this from happenning.

[Jeff_Coatsworth]

I think they called those "escaped characters" iirc - it's to tell that you really wanted that "\" character as a character and not as a command or path.

[SGRoeh]

Yes, but escape charactes usually don't show up in the actual published help. Escape characters are processed during the compiler process and aren't supposed to be exposed to the user. In my case, the "escape" character is shown in the TOC of the generated output as part of the TOC's string. It's not in the .hhc project file - it only shows up after it gets processed in the generated output.

[Jeff_Coatsworth]

What version of RH are you using?

[SGRoeh]

RoboHelp 2017 v13.0.2.334

[Jeff_Coatsworth · Accepted solution]

Ok, I'm not sure if that was the last version of RH2017, but there wouldn't be any fixes made to it to address this in that version anymore. If you wanted to log it as a bug, you'd need to confirm that it's still acting the same way in RH2020 - you could grab the trial & test with that.

[SGRoeh]

Thanks for responding and looking into this issue. A colleagure of mine may still have a trial version of RH2020 and I've asked him to test if it hasn't lapsed yet.

[SGRoeh · Accepted solution]

Hi Jeff - I was finally able to download and install the trial version of RoboHelp 2020. I converted my 2017 version of my project over to 2020, built and verified that this is not an issue in the new version so I guess no bug to log.

Thanks for all your help though.