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

Responsive HTML5 - without glossary or index

Guest
Apr 28, 2014 Apr 28, 2014

Copy link to clipboard

Copied

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?

Views

1.9K

Translate

Translate

Report

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
Advisor ,
Apr 28, 2014 Apr 28, 2014

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

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
LEGEND ,
Apr 29, 2014 Apr 29, 2014

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

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
Advisor ,
Apr 29, 2014 Apr 29, 2014

Copy link to clipboard

Copied

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?

Votes

Translate

Translate

Report

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
LEGEND ,
Apr 30, 2014 Apr 30, 2014

Copy link to clipboard

Copied

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).

Votes

Translate

Translate

Report

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 ,
Jun 25, 2014 Jun 25, 2014

Copy link to clipboard

Copied

To remove the glossary button from the Navigation Bar, open the Main.css file (template/Theme1_Standard folder) in Notepad or other text editor. Do an Edit > Find for the style div.bar_glossary. Then add another line to this style of: display:none;. Make sure to keep a copy of this main.css file outside this folder because it gets regenerated every time HTML is published.

Votes

Translate

Translate

Report

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 ,
Jun 25, 2014 Jun 25, 2014

Copy link to clipboard

Copied

Thank you!

Votes

Translate

Translate

Report

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
Explorer ,
Mar 18, 2015 Mar 18, 2015

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

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 16, 2016 Nov 16, 2016

Copy link to clipboard

Copied

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;

Votes

Translate

Translate

Report

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
Adobe Employee ,
Jan 01, 2017 Jan 01, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

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 ,
May 09, 2017 May 09, 2017

Copy link to clipboard

Copied

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?

Votes

Translate

Translate

Report

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
Adobe Employee ,
May 30, 2017 May 30, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

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 ,
May 31, 2017 May 31, 2017

Copy link to clipboard

Copied

I am using the Azure layout. I can successfully generate the HTML5 output, and other settings (like "Header>Background Color" and "Basic Settings > Default Pane" ) work just fine. I have installed all FrameMaker updates and I have tried it on another person's PC, but the same result.

Votes

Translate

Translate

Report

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
Adobe Employee ,
Jun 20, 2017 Jun 20, 2017

Copy link to clipboard

Copied

kurtd95379024 I have checked the layout that is shipped with FrameMaker and it was working. Can you share the layout .slz file that you are using with me ?

Votes

Translate

Translate

Report

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 ,
Jun 20, 2017 Jun 20, 2017

Copy link to clipboard

Copied

I do not see a way to attach the .slz file to this comment. How would you like to receive the .slz file?

Votes

Translate

Translate

Report

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 ,
Jun 20, 2017 Jun 20, 2017

Copy link to clipboard

Copied

Send him a Private Message

Votes

Translate

Translate

Report

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 ,
Oct 04, 2017 Oct 04, 2017

Copy link to clipboard

Copied

I have the same problem. I currently use FrameMaker Version 13.0.5.47 and the Azure_blue layout. It used to work perfectly fine when I had FM Version 13/Release 2015 and Update 3. I also renewed the *.slz file by downloading it again from the Adobe website. When comparing with my output generated with update 3 some weeks ago I see differences in the source code to new output genreated with Update 5. So I assume that something was changed in the compiler in update 5? How can I fix this "bug"?

Votes

Translate

Translate

Report

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 ,
Dec 04, 2018 Dec 04, 2018

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

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 ,
Dec 06, 2018 Dec 06, 2018

Copy link to clipboard

Copied

LATEST

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

Votes

Translate

Translate

Report

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