Skip to main content
Inspiring
Feb 14, 2020 6:37 PM UTC
Answered

Double-Quotes in Glossary Definitions Publish with a Backslash

Environment:

  • Win10
  • RoboHelp 2019.11 New
  • Frameless
  • Orange (modified)

 

Create this in RoboHelp:

 

How it appears in the output:

 

Problem:

The build/compile process is inserting a backslash immediately prior to each double-quote.

 

Workaround:

Use a single-quote character instead of the double-quote character; those publish correctly.

 

This is a bug, right?

This topic is closed to new replies. Start a new post to keep the conversation going.
Peter Grainge
Peter GraingeCorrect answer
Community Expert
Feb 19, 2020 8:13 AM UTC

I am advised...

This is happening while generating glossary file in output. Extra \\ is getting added as escape character. You can fix this in output by fixing the gdata1.new file in whxdata folder of output.

You will need to change the value in this file in output. 

 

As earlier, this will be fixed in the next update.

 

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

23 replies

RoboFanAuthor
Inspiring
Feb 18, 2020 11:48 AM UTC

Issue also appears for Frameless Oceanic and Dark skins.

 

Issue also appears for Responsive HTML5 output (all default settings).

Translate
RoboFanAuthor
Inspiring
Feb 18, 2020 11:43 AM UTC

To be clear, I've been running 2019.11 since the day it was released.

 

Further testing...

 

I believe this is a bug. I just created a brand new, from scratch, project. Created 1 glossary entry with definition for net cash. Here's the code from the .glo file:

 

<glossterm>net cash</glossterm>
<glossdef>Total &quot;cash received&quot; less &#39;change given&#39;.</glossdef></glossentry>

 

Added the Orange skin to the project settings. No other changes, customizations, etc. Generated Frameless output. Looked at the glossary in the output. Backslash appears. Looked at it in both Firefox and Chrome. Backslash appears in both browsers. 

 

Translate
Community Expert
Feb 18, 2020 8:35 AM UTC

I did it in the Robohelp Reimagined project at work. I'll attempt to recreate and send through.

Translate
Peter Grainge
Community Expert
Community Expert
Feb 18, 2020 8:43 AM UTC

I just tested in the current RoboHelp Reimagined (Update 11) and still not seeing it. 🙂

 

Let's see what happens in the test project when I get it. 

 

Translate
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
Community Expert
Feb 18, 2020 8:00 AM UTC

Yes I do recall smart quotes being a problem but that doesn't seem to be the issue here.

 

I am not seeing a problem with straight quotes but you and Amber are. Did looking at the glo file solve the problem?

 

@Robofan Does this happen in a new project?

 

@Amber I am assuming you set up your test in a small test project. Could you sent that to me please?

 

Translate
Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Community Expert
Feb 18, 2020 1:39 AM UTC

Yes, as per my test, smart quotes are fine. Straight quotes are the problem this time.

 

You can report problems here: https://tracker.adobe.com/

Translate
RoboFanAuthor
Inspiring
Feb 18, 2020 1:02 AM UTC

Smart quotes aren't the issue here. Just recalling an issue/bug associated with smart quotes in an older version of RoboHelp (x3?, x5?, who can remember?!) that we'd stumbled across in the past - one which, as a result, we now only use straight quotes (and even configure Word not to use smart quotes). I don't remember exactly what the issue was, but RoboHelp would add/display unwanted artifacts when we tried to use smart quotes. Bottom line, this isn't the first time I've seen RoboHelp display unwanted artifacts where quotes are involved.

Translate
Community Expert
Feb 17, 2020 12:38 AM UTC

I did a quick test. Looks like the slashes are added for straight quotes, but smart quotes turn out fine...

 

 

Translate
Peter Grainge
Community Expert
Community Expert
Feb 16, 2020 9:32 AM UTC

I'm not clear how smart quotes have come in to this. The glossary editor would not have used them and your screenshot doesn't show them.

 

Translate
Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
RoboFanAuthor
Inspiring
Feb 16, 2020 3:31 AM UTC

I'll look at the glo file, but I know previous versions of RoboHelp had issues displaying quotes if they were so-called "smart quotes" - and not the standard straight quotes. I don't believe that's the case here, but I'll see if the code offers any clarity on the matter.

Translate
Peter Grainge
Community Expert
Community Expert
Feb 15, 2020 9:45 AM UTC

I just tested the same glossary term and it worked correctly. I am not aware this was ever a problem but do you have all updates applied?

 

Otherwise, have you tried deleting the glossary term and creating it again?

 

In the glossary folder of the project there is a glo file that you can open in a text editor. It looks like this in my file.

 

<glossdef>Total &quot;cash received&quot; less &quot;change given&quot;.</glossdef></glossentry></glossgroup>

 

Maybe you can edit what you find?


www.grainge.org

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