Documentation issues

[sellar]

I'm having a problem coming up with a process to control how EA-generated documentation is chunked into files for inclusion into another document (either HTML or Word).

We have a specification that contains both non-EA text and sections that should hold EA content for a class diagram. (Obviously this is a problem because EA won't let you generate docs at the diagram level.) At the same time, we want our EA developers to be able to update on the fly, but only by generating documentation at the highest level (that is, one big document) to minimize errors.

Our original plan was to use HTML documentation, which generates individual files as well as TOCs that bring them all together. It's nearly perfect--I could create a single static link from a non EA topic to the class diagram and the rest of the links would follow.

I was disappointed to discover, however, that EA generates its HTML files as generically numbered files (EA1, EA2, etc.) and that these file names change whenever any new object or diagram is added to the EA file and documentation re-generated. Argh!

Has anyone found a way to either:

1) force meaningful names for HTML output, or
2) otherwise control the way EA chunks its documentation output

Thanks!
S. Rush
LockStream