Known Participant

Question

FM2022 HTML5 unstructured output template - Home file questions

Forum|Forum|9 months ago
April 24, 2025
4 replies
1620 views

Hello FM community,

I am creating an output template for FM2022 for HTML5 output from unstructured FM books. I have two

issues with output that I have not been able to resolve.

Issue with navigation menu entry for the home page:

We have been using this method in the past (FM2017/FM2019), and I have found that a workaround that was possible in 2017/2019 does not work in 2022.

The entry for the home page in the HTML5 navigation menu is not displaying the correct text for the home page. In past versions of FrameMaker, it was possible to save the FM document for the home page as a MIF file, search for the PDFDocInfo section, edit the Title value, remove a string of nonsensical numbers from PDFDocInfo, and save the MIF back to FM document. After doing so, the correct title would appear in the HTML5 navigation menu.

In FM2022, if I do the same process, the navigation title still does not appear correctly, and additionally, the main title of the entire document disappears completely from the HTML5 output, from the displayed content and from the source HTML pages:

Before:

After:

It also happens if I edit certain variables in the home page fm file. It appears to be irreversible. Once I edit the file in this way, nothing I do makes the title appear again.

Issue with size of the Logo file in the page output:

The size of the company logo always comes out the same--square and very small--regardless of the size and dimensions of the file that I insert in the template. I located the css page where this is controlled, and it is the one that is part of the Azue blue responsive template. I can manually edit the CSS on the output to change the div size that holds this logo, and it displays the way I want it to. However, when I add an override in Options > Override Styles for this Output, it does nothing, even if I make it important (I also tried adding it to the style mapping CSS, but that did not work either). I tried to export and reimport the entire Azure_blue layout, and edit just that stylesheet before reimporting. This ruined the output completely and I could not further edit that sts version.

Does anyone know a workaround for either of these issues?

Thanks,

Robin

Matt-Tech Comm Tools

Community Expert

Regarding the logo, I suggest inspecting the published code, and then modifying your CSS (exporting, editing, then reimporting) to address the logo formatting.

However, you may find that switching to a more recent skin gives you more/better options. Azure's a bit long in the tooth.

-Matt SullivanFrameMaker Course Creator, Author, Trainer, Consultant

R

Robin331864826nc2Author

Known Participant

How does one get new skin options? This FM version includes Azure blue and I did not see other options to select. Do I have to build them myself?

For the logo, I found the CSS that controls the div size for the logo. It's in the CSS file that is generated by the Azure skin. I can edit it in the HTML output and it changes to the desired size. But if I add a CSS file to the "Override Styles for this output" section on the Publish options to make that div larger, it outputs this override CSS file but does not take effect (even if I add importance).

R

Robin331864826nc2Author

Known Participant

I also did not see anything in the FM documentation about how to change the skin

Matt-Tech Comm Tools

Community Expert

You mention that you're setting up a template...are you describing the Use HTML Page Template option shown below?

In my experience, when creating/editing an HTML template, any missteps are very difficult to remedy.

You can try resetting your preferences (close Fm, then rename the 17 directory found in your C:\Users\(USERNAME)\AppData\Roaming\Adobe\FrameMaker directory as I did for the 16 directory, and then restart Fm)

I believe that will give you fresh publish settings, including the HTML Template.

If you can't quickly figure out the solution, you can always delete your new 17 directory and rename 17x (or whatever you renamed it to) back to 17 and restart FrameMaker.

-Matt SullivanFrameMaker Course Creator, Author, Trainer, Consultant

R

Robin331864826nc2Author

Known Participant

Hi Matt,

I did not use this template option. I meant that I am editing these sts settings to create the "template" by which I just meant the sts file with the styles and output options. In case I touched it accidentally, I did what you suggested and reset my user folder by renaming the old one. It did not change anything in the outputs, but at least I have been able to rule this out.

F

FrameMaker-dk

Community Expert

Are you adding text in the "File info" section in the FrameMaker documents? I am not sure that is the fix in this instance, but I have often used it to make the documents name work properly in HTML5 exports.

Bjørn Smalbro - FrameMaker.dk

R

Robin331864826nc2Author

Known Participant

Hi Bjørn,

Yes, thanks for suggesting this. I expected this to work because it used to work in older FM versions. I tried adding text in this File Info section. I tried both by using the FM interface and I also tried saving it as a MIF and adding the same info to the PDFDocInfo section for Title. It does not seem to work anymore in FM2022, or something else changed that I am missing.

Jeff_Coatsworth

Community Expert

Issue with navigation menu entry for the home page
I'm unsure figuring out just what you're talking about here - maybe some screenshots of what the problem is (without mucking around in MIF files or anything) and why you felt it was necessary to hack them in prior versions?

R

Robin331864826nc2Author

Known Participant

Hi Jeff, thank you for replying 🙂

One issue is that the navigation panel does not display the correct text for the first page:

Currently it is picking up a line of variables from the file. The information I have about why it was originally hacked with the MIF washing in FM2017/2019 was that it would sometimes display the filename and you could edit it to display "Home" or your chosen text instead. (I did not work here when the original workaround was documented and I could not find FM documentation about how to troubleshoot these things.) I can edit the PDFDocInfo title field by right clicking the file and choosing File Info, but there must have been some reason why the edits did not "stick" unless made in the MIF file.

If I edit the copyright variable definition that appears in this line, the title of the document disappears from generated HTML5 output.

Jeff_Coatsworth

Community Expert

It seems to be taking the first line it finds. But this is the first line of Flow B, not even Flow A.

What's the FM TOC look like?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded