I looked at 46.
There is a css in each directory, which was named for the directory. I tried renaming the css and then redirecting it to that css so that the whole project had the same css. This also did not work.
Hello again, Don
Unless I'm misunderstanding you here, you said you copied the CSS to each folder and named it identical to the folder? I'm not sure how the topic would be able to find it.
What Peter's page says should work is to have a single CSS in the project. But have that CSS inside each folder. Then, instead of having topics inside the folder point to the central CSS (which is the general way you want to work) you point these topics to the folder's CSS.
The net result is that the CSS reference should be "CSSFileName.CSS" instead of perhaps "../../CSSFileName.CSS".
Basically the issue at hand here is that when folks choose to stop using CHM files as intended (by viewing on the screen) and they choose to commit the electrons to the dead tree (paper) the process is flawed. You can thank Microsoft. Basically, the process appends topic after topic and it loses the link to the CSS file and things go downhill from there.
Another way to offer a way to reliably print is to create a PDF version of the help, then add it as Baggage along with a link to allow the user to open and print if they like.
Helpful and Handy Links
Indeed what you suggest is what I did and it did not alleviate the problem. But thanks.
Rick, I want to thank you for the advice on adding a way for the user to print the project! It worked really well and my users will appreciate this I believe.