[Doxygen-develop] Confused RTF Output

[Randall, L. <l-r...@ti...>]

I have customized the RTF style sheet to try to map to my corporate Word
styles.  The problem is that Doxygen does not use UNIQUE styles.  For
instance:

 

Body Text may be:

normal level 1 paragraph style (text)

an Include file listing (with Courier font)

an inlined name of a function or parameter (with Bold, character based)

 

            List Continue 1 may be:

                        Level 2 text paragraph style

                        "Parameter", "Returns", etc.  heading (with Bold,
character based)

                        an inlined name of a function or parameter  (with
Bold, character based)

 

The styles should be laid out so that an element ALWAYS maps to a unique
style.  Styles SHOULD NOT be modified to handle a second function.
Suggested layout, with associated text styles (shown without space before or
after):

 

Head 1 = Major Topic

Body Text 0

Bullet 0

List 0

Head 2 = Major Sub-Topic

Body Text 0

Bullet 0

List 0

Head 3 = Class, Structure, or Union  Reference ( = current Head 2)

Body Text 0

Bullet 0

List 0

Head 4 = "Detailed Description" "Public ....", "Private ....", "Member
Function Documentation", etc

Body Text 1

Bullet 1

List 1

Head 5 = "See also", Constructor & Destructor Documentation", etc.

Body Text 2

Bullet 2

List 2

Head 6 = Member Function

Body Text 3

Bullet 3

List 3

Head 7 = "Parameters", "Returns", "Since", etc

Body Text 4

Bullet 4

List 4

 

It would be HIGHLY beneficial (and would avoid many other problems) if
Doxygen permitted each style in the RTF Style sheet to be directly mapped to
a SET of specific text patterns and/or <keyword>+<pattern>.  This
could/should be in the form of a text file and/or GUI to build the text
file.  The user could then map "Parameters^p", "Returns^p", and/or "Goofy^t"
to Heading 7. Heading 7 should then assert that the next text / bullet text
/ list text would assume the level of 4 until a different level was asserted
by a header or an override.

 

Regards,

Larry Randall

******* Documentation