Thanks for the reply, but that's not it.
1. RoboHelp adds "class=p" to the <li> tags. If you
manually take it out, RoboHelp puts it back in. (They finally got
rid of the kadov tags, but they still put a lot of completely
unnecessary crap into the HTML.)
2. As I said in my original post, when you open the
uncompiled .htm file in a browser, the numbers are CORRECT. The
problem occurs only after the file is compiled (either as a .chm or
as Web Help). Since the uncompiled HTML file is displayed
correctly, it's obvious that the class is not causing the problem.
If the HTML protocol were negating the setting, we'd see the same
display in both compiled and uncompiled. (Also, the fact that the
inline formatting was ignored should also indicate that it's not an
HTML protocol setting issue.)
***ANSWER***
When RoboHelp recreates the .css for use with the compiled
files, it's stripping out a line.
We create both .chm files and Web Help projects, and this
problem exists in the compiled version of both. So I started
looking at the compiled Web Help files (since they're flat files)
to find the answer.
When you compile a Web Help project, RoboHelp creates yet
another version of the .css. Here's a comparison:
-> ORIGINAL VERSION (used with the uncompiled files):
ol ul ol li
{
list-style-image: none;
list-style-type: lower-alpha !important;
}
-> VERSION CREATED FOR THE "OUTPUT" DIRECTORY
(used for the compiled files):
ol ul ol li {
list-style-type:lower-alpha; }
RoboHelp removed the "list-style-image: none;" setting. We
need this line because we use an image for our bullets, and the use
of an image is inherited. So, by default, all lists that are nested
within a <ul> will continue to use that bullet image unless
you explicitly "clear" it with the "list-style-image: none;"
setting. If an image is used, that image overrides any numbers or
letters that might be displayed.
**WORK-AROUNDS**
1) Obviously, we can stop using the bullet image, and that
would fix the problem for both .chms and Web Help projects. But
it's a bummer to have to change our style because of a RoboHelp
bug. :-(
2) In Web Help projects, I can fix the problem by replacing
the .css file that RoboHelp puts in the output directory. (I've
tested this and it works.) But this doesn't fix the .chms, and it
adds a step to the release cycle. (We've got a small doc
department, lots of products to support, and very aggressive
release cycles.)
If anybody has any work-arounds for the .chms, I'd be
interested.