Hi Paul,
No way will this ever be fixed using the main functions of eaDocX. Everything works using an (element type + element stereotype) combination, so the whole thing would explode.
But don’t dispair.
There was a feature in v5 which uses little bits of script to basically do anything: print any bit of a Word document, ijn any style, using any bit of EA data, and using any rules you can think of. I have not yet put this into eaTeamWorks (nobody needed it until now) but as you have asked so nicely, I’ll find the code and put it back.
I will also use your example of a secondary stereotype of a <>Class as a test case.
But will take a few days to implement, so go on your holidays, and it will be ready when you get back.
