FrameMaker: Listed Numbers Serif Font, Text is Sans Serif?

[charless80395138]

Does anyone know why, after HTML5 output, my listed numbers are serif but all my text is sans serif? Thanks.

[Matt S - Tech Comm Tools · Accepted solution]

The reason your numbers are in Sans Serif is because the default CSS doesn't specify a base font.

(Yes, it would be nice if Adobe fixed this. I've requested this previously at adobe.com/go/wish, and you should do the same)

You can add either a body or html entry that specifies the font you want to use in your base css to remedy this.

More complete instructions on this are in the Manage CSS section in my post at

https://techcommtools.com/formatting-branding-html5-content-framemaker-2015/

-Matt

[charless80395138]

Thanks Matt, I'll try adding a html or body entry to my base css and see if it works.

[CaptLauren]

When I look at the source in my HTML5 output for am FM file that is  part of a book, I see that it's referencing several different stylesheets: rhstylemapping.css, one that is dedicated the particular file in my book, Styles css (in the responsive_html5_!OverrideStyle! folder, and editstyle.css.

How do I ensure that there is only one stylesheet for the whole book?

Thank you!

[Jeff_Coatsworth]

Make sure that all your CSS is in one referenced CSS file and then just delete all the others - there will still be references to them in the HTML5 code, but if they don't exist, they are ignored. 

[CaptLauren]

Thank you so much for your swift response! I will give it a try.

[CaptLauren]

Unfortunately, Publisher is ignoring the CSS file that I imported, and instead uses the rhstylemapping.css, one that is dedicated the particular file in my book, and editstyle.css. It is NOT using the combined style sheet I created.

Is there something I'm missing? Output settings?

[Jeff_Coatsworth]

If rhstylemapping.css is the first one referenced in the published HTML5 output, make sure you've copied the contents of any other CSS files referenced into that rhstylemapping.css (use Notepad) & then delete the other CSS files from the published output. That way you'll have 1 file being referenced that actually exists and several others that don't (and therefore won't be used).

[Matt S - Tech Comm Tools]

You'll want to ensure your Fm styles are mapped to CSS styles via Publish pod, and then export your rhstylemapping.css, edit, then reimport it.

Any unmapped styles will have the FM_ prefix in the html, and the properties of your FrameMaker style will be (loosely) stored in a CSS that's saved on the fly.

[CaptLauren]

Perhaps I should move this thread?

I am still getting multiple css file outputs. For testing purposes, I am publishing just a single FM file from my book. I deleted all but the custom css but they are still referenced in the Frame Source code.

Having contacted TechSupport, it appears that I must import my custom CSS file into Publisher settings using the Manage Style feature, and indicate that it is also an override style sheet.

Also FM V2020 is "missing" the Combine Stylesheets feature. I'm afraid that Adobe is having significant growing pains. And, I wonder how well the FrameMaker engineers are communicating with the RoboHelp engineers?

Also, do the CSS files belong in the source content folder, or in the output folder?

[Matt S - Tech Comm Tools]

A new thread is probably a good idea. This one is from 2018, so if your problem isn't related to serif fonts in numbered lists, it'll be easier to understand in a new thread.

* For anyone finding this message, I believe mapping the para styles to CSS is one of the main issues CaptLauren is having.