CSHelp_Hook changes from FM12 to FM2019?

[kbalatincz]

I publish responsive HTML5 online help for my company's software. When I started using FrameMaker, it was with FM12 which handled hooks and filenames very well. When we upgraded to FM2019, I cannot follow the same steps and get the same results. We need a constant file name for each page (*.htm) file in the responsive help. In FM12, the CSHelp_Hook allowed us to specify a constant name for the page's filename in the help. In FM2019, it ignores the hook and always uses the section header as the filename. This is okay for our English version but we send out for translations. When the file is translated, it tries to use section header, which is now not English, instead of using the untranslated file name that we need it to use. Any idea of what might be going wrong and how to fix this?

[Amitojsingh]

Sorry but from what i understand the issue is around the file naming. Does topic name pattern in Style Mapping -> General Settings help? If not, please share more details on the specific issue so we can look into it.

Thanks

Amitoj Singh

Email: amisingh@adobe.com

[kbalatincz]

Maybe, what should the settings on that page? The only thing I was instructed to ensure to have checked was "merge topic styles into single CSS". Should I check "split into Topics using Marker"? If so, what do I enter for marker type?

[kbalatincz]

Hi, brief update, in FrameMaker 2012, we did split topics using the CSHelp_Hook marker; however, FrameMaker 2019 ignores the CSHelp_Hook and writes out the file names based on the value in the "Topic Name Pattern" field which used to be left as "Default" but that value now gives us different output. I will try all four of the options to see if any of them work for us.

[kbalatincz]

Another brief update: changing the Topic Name Pattern to any of the available options did not fix our issue. Additional support needed.

[Jeff_Coatsworth]

DM Amitoj, e-mail him or send an e-mail to the FM folks at tcssup@adobe.com.

[Amitojsingh]

Kindly email me at amisingh@adobe.com so we can connect and work on debugging this further