Missing hypertext markers in Responsive HTML5 output

[BertaEmil]

Dear community,

we publish some of our FrameMaker documents as Responsive HTML5. As we describe a quite complex software with many parameters, we inserted Hypertext markers for nearly every parameter in the FrameMaker files. Reason: from the software we want to jump directly to the corresponding description on the HTML page. With FM 2019 everything works as expected, with FM 2022 (17.0.6) the Hypertext markers are missing in the HTML files (so there is no "a" element with the content of the hypertext mark as "name" attribute). Any ideas?

Many thanks in advance, Andreas

[Jeff_Coatsworth]

Are these missing markers in newly created FM2022 docs or upgraded FM2019 ones?

[BertaEmil]

Dear Jeff,

Many Thanks for your inquiry. The actual documents were converted from FM2019. However, it makes no difference to us (I just tested it) – even after starting with a document from scratch in FM2022, no corresponding anchor is created for a hypertext mark in the HTML output.

[Winfried Reng]

Hi,

Can you tell us which hypertext markers you use?

The marker name is Hypertext, isn't it?

And what is a marker content (just an example)?

Best regards, Winfried

[Winfried Reng]

When I inserted some hypertext markers with just "hypertextmarker1" (running number) in the FrameMaker file, I could not find anything with "hypertextmarker" in the created files. As @BertaEmil had reported.

[BertaEmil]

Hello Winfried,

I'm working with the German version of FrameMaker, so I hope "my" English terms are correct: The "Marker type" is "Hypertext" an the "Marker text" is something like "DP234" (no spaces, no umlauts, nothing special).

Many thanks for your valued input and best regards, Andreas

[Winfried Reng]

Hi Andreas,

Hm. Then I really think that this is a bug.

You could test, if also other markers are not converted. Create a new marker type (something unique, e.g. testtest or something like this) and insert a marker. Then convert. Can you find this testtest in all your converted files?

The conversion to HTML5 had changed in the last FM versions. Therefore it could be that this new bug was inadverdently introduced.

Best regards, Winfried

[Winfried Reng]

In the online help there is also the option to insert TopicAlias markers for online help:

Insert | Publish Marker | Apply CSH marker.

https://help.adobe.com/en_US/framemaker/using/using-framemaker/FrameMaker-2022/user-guide/WS2d2a1705...

Possibly this is an alternative.

Best regards, Winfried

[BertaEmil]

Hello Winfried,
many thanks for your input and your workarounds. Some brief tests have shown that other markers ("own" marker types) are also missing in the output files.
The TopicAlias markers generally work as long as there are at least anchors in the output files.
But I'm probably too stupid to understand the structure of the generated header file: In FrameMaker I add a marker of type "TopicAlias" with the marker text "DP123" for example. In the HTML output the following anchor is inserted: <a id="CSH_2" name="CSH_2">. In the corresponding header file, genereated by FrameMaker during publishing, is a line "#define DP123 1". So I'm not sure how the software could jump to the anchor in the HTML file, because neither "1" nor "DP123" could be found there. I think I will report this to Adobe.
Many thanks again and best regards, Andreas

[Winfried Reng]

Hi Andreas,

I found my markers in csh.js.

But I a not an expert and do not know, how to use this.

There are some other experts here, who might help.

Best regards, Winfried

[Jeff_Coatsworth]

That's because the resulting JavaScript using that .h file to translate calls to locations in the HTML - it's called a Map ID table. Your application calls using the TopicAlia marker text [DP123] and it [the JS in the output] converts that call to the Map ID [1], then it has an internal map file that says 1 = some URL path to the topic with that marker you put in,
This all comes from the RoboHelp rendering engine that lurks under the hood in the FM Publish to HTML5 hood.

[BertaEmil]

If I understand you correctly, the next step would be a test, simply changing some of the "Hypertext" markers to type "TopicAlias"? And testing the newly published HTML files with the software?

[Jeff_Coatsworth]

Yes, I'd give that a try - do you know what method the application is using to call the CSH topic pages?

[BertaEmil]

As suggested I changed a Hypertext marker to a TopicAlias marker. In the source FM file "FM22/2.4.fm":

• Marker type "TopicAlias" - Marker text "DP319"

In the generated Header file "FM22.h" there is the following line:

• #define DP319 1

In the generated HTML file "FM22/2.4/2.4.htm" there is the following anchor where the TopicAlias marker sits:

• <a id="CSH_2" name="CSH_2">

And in the generated Javascript file "csh.js" one could find the following entry:

• <item mapid=\"DP319\" mapnum=\"1\" topicurl=\"FM22/2.4/2.4.htm#CSH_2\" />

After publishing we copy the contents of the output folder "Responsive HTML5" to a different folder structure. With FM 2019 the following call in the software works for the topic - with Hypertext marker and marker text "DP319" (as you probably know, there is a prefix "HT_" automatically added to the marker text in the HTML file).

• file:///E:/Temp/FM22/Docs/index.html#t=FM22/2.4/2.4.htm#HT_DP319

Now I'm not sure how the call for FM 2022 should look like. The following idea doesn't work.

• file:///E:/Temp/FM22/Docs/index.html#t=FM22/2.4/2.4.htm#DP319

Do you think the header file is needed? Because it is placed in the folder above the "index.html" and all the other files of the HTML output. Of course I could share all source files and publishing settings here if helpful.

[Jeff_Coatsworth]

Try index.htm?rhmapno=DP319

[BertaEmil]

Thank you very much, that was another tip in the right direction. After some further tests I think it has to be called rhmapid, not rhmapno. That seems to work, the page with the corresponding anchor #CSH_2 is shown.

[Jeff_Coatsworth]

What about xref markers? Do they survive into the HTML5? Have you checked the Publish settings? Your FM2019 sts file settings may not have survived upgrading to FM2022.

[BertaEmil]

I'm not sure I understand what you mean by "xref markers". "Normal" cross-references to chapters or images work as usual in the HTML output. This also applies to xrefs between different files within the book. Unfortunately, I can't find anything about this in the sts settings file, and it doesn't matter whether I create a completely new sts file.