This was not helpfull enough
Okay, so it can be done via the normal.rtf
(I wonder why the numbering doesn;t work in the first place...)
So what to do with it?
There is only one poor paragraph about the normal.rtf, and no mention on how to fix numbering. They mention you can edit numbering, but how, they forgot.
A step to step tutorial would be very welcome.
I opened the normal.rtf via File > Open source file
and I did see a right mouse menu > Edit > List and Overrides
but can't figure out what to do.
That's why a manual would be handy.... :-/
I fixed a lot of numbering issues, after trying all your suggestions (which didn't do the trick for me). What I did was in the very first template, set up this :
1. Cow
1.1 Color of cow
1.1.1 Black is color of cow
1.1.2 White is color of cow
1.2 Legs of cow
1.2.1 Four is legs of cow
2. Cat
2.1 Color of cat
2.1.1 Black is color of cat
2.1.2 Red is color of cat
2.2 Legs of cat
2.2.1 Four is legs of cat
And then for every position that I wanted a numbered header, I put this schema in. Then generated the documentation, to see if the numberen was increasing. If so, I changed the right header into the one that I needed. This worked out fine, with one exeption.
I have multiple scenario's and whatever I do, it won't go right.
I have a demonstration later this day about EA and why we should use it. And of course that decision is also made on the documents that come out of it. I have to say, the generation of Use Cases and other documentation has improved a lot, but is still not ideal.
I was writing some PHP program to generate documentation based on an extorted XMI of my model, and I was able to generate decent documentation within a few hours. If I can do this, why can't EA do some decent documentation generation?
I now have this situation where numbering works correct, and only for scenario's it isn't good. Even if in my template between the scenario tags I have a header1 with a format "1." the generated document shows "1.1.1" Grrrrr...
