Skip to main content
A
Anonymous
April 28, 2014
Question

Responsive HTML5 - without glossary or index

  • April 28, 2014
  • 6 replies
  • 2380 views

I'm trying to generate Responsive HTML5 through FM 12 (without RH). Does anyone know if there's a way to disable the glossary and index? Will I have to dig into the code, or is there a function in FM that lets you stop it from being generated?

This topic has been closed for replies.

6 replies

B
bluegiraffe24
Known Participant
December 4, 2018

I have the same issue. I can't remove the glossary, index, or filter by just making them "false".

Matt-Tech Comm Tools
Community Expert
Matt-Tech Comm ToolsCommunity Expert
Community Expert
December 6, 2018

Can you please try creating a new layout, or using a different layout style?

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
Ritkumar
Adobe Employee
Ritkumar
Adobe Employee
January 2, 2017

Hi,

You can also disable the Glossary and Index options from the layout via layout customization.

Goto - Edit Settings > Responsive HTML5 > General >  Manage Layout > Edit >

Sharing the option from Azure Blue layout -

Thanks

K
kurtd95379024
Participant
May 9, 2017

Using the Layout Customization recommended by Ritkumar, I am setting the "Show Glossary" and "Show Filter" to False. But these are still showing up when I generate the output. Has anyone else had this problem?

Ritkumar
Adobe Employee
Ritkumar
Adobe Employee
May 30, 2017

kurtd95379024​ Which layout you are using and does the customization finishes successfully ?

D
DiegoJer
Participant
November 16, 2016

In the directory containing the published Responsive HTML5 output, edit the /template/[Template_name]/usersettings.js file, and change the variable values:

var useGLO = true;

var useIDX = true;

to:

var useGLO = false;

var useIDX = false;

deborahsauer
deborahsauer
Inspiring
March 18, 2015

I removed the Glossary button by opening the Index.html file and deleting this line:

<li class="wTab" id="gloTabButton" data-contentid="gloTabPane" onmouseout="onTabHoverOut(this, 'tab')" data-class="wTab" ontouchend="onTabHoverOut(this, 'tab')" onclick="selectTab(this, 'tab')" ontouchstart="onTabHover(this, 'tab')" data-classhover="wTabHover" style="display: inline;" ontouchmove="onTabHoverOut(this, 'tab')" data-classsel="wTabSelected" onmouseover="onTabHover(this, 'tab')"><img src="template/Theme1_Standard/glo.png" class="normal" alt="Glossary" title="Glossary" id="xmlEditorGLOSidebarButton" style="border: none;" border="0" /><img src="template/Theme1_Standard/glo_hover.png" class="hover" alt="Glossary" title="Glossary" id="xmlEditorGLOSidebarButtonHover" style="border: none;" border="0" />

This has to be done after generating the HTML5 because FM overwrites the file every time you generate.

    Arnis Gubins
    Arnis Gubins
    Inspiring
    April 30, 2014

    These are hardwired in the settings.sts file. This is a zip container that holds all of the code required for the screen layout. If you're comfortable editing XML, DTD's (.slp files in the sts), and javascript, then you could work your way through the layout to remove these components. It's not a trivial task.

    F
    FieryPantone
    Legend
    April 30, 2014

    Vanishingly unlikely I'll get to play with these new options, but I'm still curious :-} what FM content is the HTML 5 conversion identifying as glossary and index data, or does it just generate glossary and index containers whether or not there's anything identified to put in them?

    Arnis Gubins
    Arnis Gubins
    Inspiring
    April 30, 2014

    Niels,

    The containers for Glossary and Index are hard-coded into the pre-defined screen layouts. You can edit the contents of the STS file by unzipping it and tracking down and expunging all occurrences of the Glossary and Index usage throughout the various javascript and definition files and then save these as a new custom sts (after re-zipping).

    F
    FieryPantone
    Legend
    April 29, 2014

    very speculative reply, and from no knowledge of FM12 … have you tried Exclude (right-click option on .book component) on the glossary and index?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices