Question mark icon instead of space in chm after RH Upgrade 2022 version

[Kdale2]

After upgrading to RH 2022.4.179, we have some spaces, apostrophes, and other random areas that are showing as the triangle with the question mark. We checked and the Window OS is set to English and the Preset Output is set to English. These are old .chm files that we continually update. We also looked at the HTML and there is nothing in there to indicate a problem. Examples attached.

[KdaleCaptivate]

Hey, this is also Kdale2 bcz I somehow messed up my account and haven't had time to fix it or merge accts since my work emails and companies merged (send help) Ugh... Anyway, we encountered this with the copyright symbol, apostrophe, dash, and extra space. There might have been other symbols/punctuation marks that I didn't catch.

As a temporary fix, we removed the copyright that we had as a footer in each help topic by removing it from Layout. When we removed it, it seemed to fix the issue.  It's been a while since I did it myself, so here's what one of my writers told me she did to remove the footer and fix the issue: "For the Output, you select None in the Topic Layout (and I've also been setting Language to English (US) because I read originally that would fix it but it didn't). Then you select all topics in the project, select the ellipses on any topic to display the Multiple selection (whatever the name is) and then set Topic Layout and Language to Default (which is now None). Sometimes it takes a while to save All topics. Then, regenerate with no footer. "

[RH_TIW]

Browsing through mine the big standouts are:

• The restricted symbol (HTML code: ®)
• The trademark symbol (HTML code: ™)
• Instances of double spacing between paragraph tags.
• Empty paragraph tags ( <p></p> ) within the document.

[Peter Grainge]

Empty paragraphs is a different issue. See Item 32 here.

________________________________________________________

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

[Herbert25202231ndcw]

I have the same issue and also waiting for a ADOBE solution but I have 2 workarounds:

1) As mentiond create the chm file was version 3

2) Duplicate the output preset (masterpage). Remove the line with utf-8 from the masterpage in the folder assets and save. Create the chm file with this masterpage.

Line removed => <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

For now I see no side effect.