Fonts in TOC

[Cynthia Pao]

I'm using RoboHelp 2022.5.28 fo rmy help system, and I have a problem with the fonts in my output header and TOC.

Here is a screen shot:

The fonts in the topic content are correct, and they are Roboto. In the TOC and header, though, it's Times Roman. This happens when the help is embedded in the application. If I double-click on the index.html file and open it in a browser, the fonts are fine.

I believe there are extra carriage returns in one of the files that causes this (maybe?). Has anyone see this before?

Thank you!

Cindy

[Peter Grainge]

This seems more like an issue with the way the developers are calling the help. Maybe they are not embedding all the output or they are using a lightweight browser, if that is the correct term.

I'm not clear why you would think it is down to some line breaks.

Either way, If it works correctly when opened in a normal browser, then your help is good and it is a developer issue. I don't think I have seen it reported before.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[Jeff_Coatsworth]

Yeah, I suspect it's the browser they're using - some will do a font family substitution that you may not like. 

[Cynthia Pao]

In the distant past, there was an issue with line breaks, and we thought we fixed it, so I assumed it was the same now.

But when I open the file, it looks fine. 

I now believe it is a browser problem. The file looks right in Edge, but not in Chrome. That complicates things because the application runs in Chrome.

[Peter Grainge]

It seems Edge can handle how your developers have integrated the help but not Chrome. Again, that is something they have to resolve. If it works locally in both browsers, that is your job done. 🙂

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[Amebr]

The TOC is in an iframe I believe, so maybe the font is running in to cross site scripting issues? I assume in an embedded help scenario it would be an iframe inside an iframe, which might be where the sticking point occurs. Your developers would need to look in to that.