1 person found this helpful
The _ns stylesheets are a curiosity of RoboHelp 7. On output, RH examines your css and creates a copy in the _ns style sheet. It then deletes all styling that it thinks may give compatibility issues. If I remember correctly, Firefox, Netscape and Opera use this style sheet.
What I did in the _ns style sheets, was after publishing replace their contents with an @import statement. For example. Your style sheet is called mycss.css. In your output you end up with two style sheet: mycss.css and mycss_ns.css. Replace the contents of mycss_ns.css with @import "mycss.css"; Your style sheet then imports the styles from the original style sheet.
This is a bit arduous since you have to replace the css every time you create the output, but you don't have to fall back on ugly workarounds. Does this solve your problem?
replacing or editing the stylesheet every time I generate is not really something I want to do.
I guess I could include it in the same Final Builder project that I use for generating all my languages, but that is getting a bit heavy with the Arabic and Hebrew tweaks and a couple of different outputs with diffferent build tags.
sooo, you answer the question, but I wish there were some other answer
When you have a script that does that for you, it's no work at all to modify the output. I believe quite a lot of people have find and replace macro's or something else to make the output just that bit better.
Have you checked that the import fixes the problem? If not, something else may be amiss and we need to dig a little deeper.
Yes, replacing the content of the _ns.css file with @import "styles.css"; seems to fix the h2 style.
I need to test this a bit to see how to do it in practice... automated, and not increasing my "build time" too much. Better apply this after our current release, if my job still exists next year.
There's no harm in doing it in all my 34 languages, I hope.
There's no risk at all. It only make sure that your original style sheet is used. Nothing more, nothing less.