Context-sensitive help broken in FrameMaker 2022

Question

I am using a .h header file that is provided to me by the development team, putting it along side the .book file, but when I generate the HTML5 it no longer generates the CSH mapping. All calls to the CSH URLs go straight to the default page. This worked flawlessly in FM 2017.

I've noticed that the .h file that is added to the FM output folder has an extra line added at the end with a marker that doesn't exist, and that the .ppf file doesn't contain any <contextentry> nodes like it used to.

Has anybody got CSH working in Responsive HTML5 with a provided .h file in FM 2022 ?

Jeff_Coatsworth · Accepted Answer

Yes, the files use an identical format. However, I think I have narrowed it down to a change in the way FM interprets the .h files.
#define<space><marker_text><space><space>...<space><space><MapID#>

If I replace the spaces with a single tab, then it seems to work as designed:

#define<space><marker_text><tab><MapID#>

It does not work with a single space or multiple tabs.

So this is definitely a regression in the way FM has become stricter in parsing the .h files.

I'm pretty sure it's always looked like that - I say that because, under-the-hood, the FM Publishing engine is still just a headless version of the RoboHelp Classic program. In RH, it's always looked like that (speaking as a FM to RH import sort of guy). Whatever .h file supplied to you should have matched the generated .h file. Maybe the parsing was looser, but the expectation has always been that you match the generated file format.

Jeff_Coatsworth · Answer

Are the Map IDs present in your FM CSH marker content?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded