Finally, I understand the problem.
You want a bulleted list with a custom bullet.
Each item has dropdown text, which is a numbered list or
maybe a combinatiion of numbers, bullets and plan text.
When you use a custom bullet, the output turns all the tagged
dropdowns into custom bullets.
You probably can't straighten this out in RH, because output
code doesn't look like the TrueCode. RH output overrides any
changes you may try in TrueCode.
You can, however, handle this by brute force. After
generating WebHelp, you can go into the output html code. The tags
must tell the browser to end the bullet list -- </ul> --
before it reads the popup code.
Then you have to insert a tag -- <ul> -- and a style
statement telling the browser the next line restarts the custom
bullet list. Again, you have to cancel the custom bullet ahead of
the code for its numbered dropdown.
And so on.
Why it works OK for regular bullets is hard to answer, except
that RoboHelp output processing uses different methods for regular
and custom bullets, and RH programmers didn't anticipate this
situation.
If you don't want to fool with the output html code, you have
some options.
One, obviously, is to go to regular bullets for the master
list.
Another is to abandon dropdowns and use text-only popups,
which will require some manual work for a numbered list.
Then you could put the special text into a very small topic
and call it in an automatic-sizing popup window, or specify the
size yourself. With the special text broken away from the master
bulleted list, you have endless opportunities for styling both.
Opening a new topic and inserting the special text doesn't
take much more effort than opening a popup dialog and inserting
text there, does it?
If you want to see a sample of the brute force method, please
send me a private message.
Harvey