"See also" formatting in index shows up in HTML5 output

[snevhead]

I have any "see" or "see also" occurrences in my index markers set to italic format.

Using one HTML5 layout (Theme1_standard), this is simply ignored in the HTML5 output. This is not great, but I can live with it.

Using another HTML5 layout (Charcoal_Grey), the format tags are displayed in the HTML5 output, which is awful. See attached screenshot for a comparison of the two outputs.

There doesn't seem to be a way to tweak this in the Publish Ssettings, especially since the paragraph formats used in the index file (the standard Level1IX and Level2IX) aren't listed on the Style Mapping tab of the Publish Settings dialog, so I can't manipulate them at all.

If I manually remove the italic formatting from my index markers in the source files, the HTML5 output looks better but my PDF output suffers. Anyone know a workaround for this?

[Winfried Reng]

Hi,

Do you have the latest FrameMaker update 17.0.5?

Can you check in the Help menu in About?

In the output folder there are also some HTML5 files with scripts and layout data. Could you search in these files for one of your index items in both layouts and check what is different in your layouts? You might add something like ")))" to your index text to find it more easily.

Best regards, Winfried

[snevhead]

I'm running version 17.0.3.546. will do an update real quick and see if that helps.

I tried looking in all the scripts and layout data for mentions of the index items, but I couldn't see what was different. might need to look harder. I was checking the HTML files themselves, to see what the markup was (although FM markup is pretty inpenetrable). I also checked for any configuration files in the fminit install folder, but wasn't successful...

[Jeff_Coatsworth]

How is your CSS set up to handle those IX paragraph tags? That's probably where you will be able to control the styling of them.

[snevhead]

I mean, the CSS that is outputted with the HTML5 is just a written record of anything I've selected or configured in the Publish Settings dialog, no? There is no entry in that output CSS of the IX paragraph tags.

I try not to manipulate the CSS by hand, if I can help it. if the format tags don't show up in one layout, they shouldn't show up in the other, imo.

[Jeff_Coatsworth]

Ok - how about a second set of IX files conditioned on "Online" or "PDF" (exclude one in the book when creating the other) - that's probably your fastest way to deal with the differences.

[snevhead]

Yeah, that's probably the long-term workaround. It just involved changing a lot of index markers by hand, which I was trying to avoid. It's a huge book. I'm always amazed at how much we FM users are willing to do "on foot".

Thanks for your help!

[Jeff_Coatsworth]

For what it's worth, you get a lot more control over your HTML5 output if you go the FM to RoboHelp route and generate from within RH.

[snevhead]

Yeah, that's becoming clear to me. Almost all "advanced" problems I have are because of RH features being included with FM but not fully integrated (or at least, not configurable).

Thanks again!

[FrameMaker-dk]

When you set up your sts file for html5 publishing... have you made specific settings for the character style you are using the "See" etc ? Like this:

[snevhead]

No, for both templates it's just specified to "Use source style". I didn't make any additional configuration changes.

[FrameMaker-dk]

I would suggest that you apply a formatting to the character style (Italic) in the HTML5 setup then, and try again. The CSS styling in the FrameMakers HTML5 publishing tool is quite effective.  When I develop my templates I add extensive formatting to the STS file, so that customers can replicate the look and feel of the printed publication in HTML5

[snevhead]

I'll try that, thanks.