Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

TOC not showing up in HTML and Index and Glossary showing up

Community Beginner ,
Nov 26, 2018 Nov 26, 2018

When I publish to Responsive HTML5 in unstructured FrameMaker Version 13.0.5.547 the TOC doesn't come through even though I have it marked as "true" in the settings.

I don't want the Index or Glossary to come through, so I have them set to "false" but the icons for them are still coming through into HTML.

Capture.JPG

457
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Nov 28, 2018 Nov 28, 2018

Are you expecting the TOC to display on on page, like they do in a PDF?  If so, I don't think you can get that in HTML.  The TOC displays on the left in a a column, at least for me.  It never displays on the right.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 28, 2018 Nov 28, 2018

Depends on the layout used and how much you want your web developers to mess around with them.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 28, 2018 Nov 28, 2018

Yes, that's what I was expecting. If it's not possible for the TOC to come through as a page, that's fine.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 28, 2018 Nov 28, 2018

We don't have web developers. I'm it. I chose "false" for Index, Glossary, and Filter, and the icons for them continue to show up so users can click on them and then go to a useless area. That makes no sense. FrameMaker doesn't seem to be working correctly.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 01, 2024 Aug 01, 2024

The TRUE and FALSE settings control the visibility of the icons for those components in your HTML output.

When set to TRUE, the icons will take you to those components, which generally get processed into special areas on the output, rather than displaying as actual topics. 

 

If you don't have a glossary, for example, you should set Show Glossary to False so that your users aren't confused by the icon's inclusion in your output.

-Matt Sullivan
FrameMaker Course Creator, Author, Trainer, Consultant
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 04, 2024 Aug 04, 2024

I'm pretty sure that a recent Windows update has made my Responsive HTML output get all messed up. Perhaps yours has also fallen foul of something similar? Has this worked before?

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 15, 2024 Aug 15, 2024

What do you mean by all messed up?

-Matt Sullivan
FrameMaker Course Creator, Author, Trainer, Consultant
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 15, 2024 Aug 15, 2024
LATEST

Right after a Windows update my HTML output was showing a cross on some chapters rather than content and other pages that were shown in the TOC were not accessible by clicking on them. Numbering that previously worked started behaving differently too. Yesterday I found out about saving FM files as .MIF then back to FM and that seems to have sorted out most of the issues. I fixed the numbering by taking a different approach with it.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines