generated TOC navigation bar no longer works in Responsive HTML5

[Daniel25310388xr77]

Hello,
when generating HTML5 in the current version 16.05.1096, the generated TOC navigation bar no longer works. The faulty link does not lead to the .htm or the scripted ID, but to the programme folder:
file:///C:/c:/program%20files/adobe/adobe%20framemaker%2020/filters?rhtocid=_4#998464bc-3
How can this be fixed?

[Jeff_Coatsworth]

That's not the current version - FM2022 (v17) is the current one.

[Daniel25310388xr77]

There is no version 17 in the software and the message "current" appears.

[Jeff_Coatsworth]

I suspect you're on subscription (because I don't recall when perpetual licensing was phased out for FM) so you should have access to the new version through that.

[Daniel25310388xr77]

I was able to install version 17 now, but unfortunately nothing has improved in the generated HTML5.

[Matt-Tech Comm Tools]

Can you share a screen shot of the output and also of your Fm book?

[Daniel25310388xr77]

[Daniel25310388xr77]

This is the fals path in toc

[Jeff_Coatsworth]

Yeah, we got that - let's see the FM book - are all the other links working in the output?

[Matt-Tech Comm Tools]

What does the published HTML look like before you click on the path, and what does your book file look like in FrameMaker?

[Daniel25310388xr77]

[Jeff_Coatsworth]

That doesn't look like a generated TOC - did you manually create it and the links inside it?

[Jeff_Coatsworth]

Let's split you out into your own thread.
Let's see how you've configured your Settings to create the HTML5 output.

[Daniel25310388xr77]

I have the same sts as version 16. With the new default.sts comes same problems in the navigation.

[techwrite]

Hello, 
I am trying to publish Responsive HTML5 from FrameMaker for the first time.
I have the same problem with the same FrameMaker version 16.05.1096 as described above (the generated TOC navigation bar does not work. The faulty link does not lead to the .htm or the scripted ID, but to the programme folder:
file:///C:/c:/program%20files/adobe/adobe%20framemaker%2020/filters?rhtocid=_4#998464bc-3).
Is there already a solution for this?

[Jeff_Coatsworth]

We never heard back from @Daniel25310388xr77 , so we don't know. Do you have a manually created TOC or is it generated?

[techwrite]

It is a TOC generated by FrameMaker automatically.

[Jeff_Coatsworth]

And the TOC entry works fine in FM? Is it only one of the TOC entries that is misbehaving in the HTML5 or all of them? 

[techwrite]

The TOC entry works find in FM and generated PDF.
The misbehavior in HTML5 affects all TOC items.

[Jeff_Coatsworth]

OK, in that case, it must be something in the Publish settings for HTML5. Have a look in there to see how it's set to convert those TOC paragraph tags.

[techwrite]

Where can I find the settings for converting the TOC paragraph tags? Is this the correct place?

 

[Jeff_Coatsworth]

Yes, I believe that's the spot.

[Matt-Tech Comm Tools]

Special characters (like code or punctuation) is often difficult to display in HTML.

Since you're using code in your document, can you please share the HTML code for the highlighted portion of the TOC?

[Jeff_Coatsworth]

Are you thinking it's the ulauts that are throwing it off Matt?

[Matt-Tech Comm Tools]

No, I'd expect the umlauts would be treated as any other text character. However, characters used in HTML/XML/SGML markup will cause issues if not properly presented.