Context-sensitive help broken in FrameMaker 2022

[nicholasb56967193]

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]

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

[nicholasb56967193]

Yes of course. The CS help system worked perfectly with FM 2017 and nothing was changed except from updating directly to 2022.

[Jeff_Coatsworth]

Ok, just checking - maybe something had gotten messed up in the FM content when it was upgraded. Were you creating Responsive HTML5 output in FM2017?

[nicholasb56967193]

Yes.

I was wondering if anyone else was having problems with CS Help in the latest versions of FM when providing the .h file.

The CS help seems to generate fine if I omit the .h file and FM generates its own one. However, that isn't an option with my development team as they insist on providing it themselves with their tools.

The inability to properly generate the CS help mapping with a provided .h file seems to be a regression in the latest versions of FrameMaker.

[Jeff_Coatsworth]

Aren't both .h files identical? They should both be laid out with a
#define   marker_text   MapID# 

structure, right?

[nicholasb56967193 · Accepted solution]

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.

[Jeff_Coatsworth · Accepted solution]

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.

[Robert_^_W]

This has completely fixed my issue with FM 2022. We had decided not to upgrade based on the context points no longer working. A simple find <space>1 and replace with <tab>1 was all I needed (all my points start with number 1). Thanks for the pointer.