rtf generation (Origin: bugzilla #782754)

[doxygen]

status ASSIGNED severity normal in component general for ---
Reported in version unspecified on platform Other
Assigned to: Dimitri van Heesch

On 2017-05-17 18:38:43 +0000, Lawrence Leinweber wrote:

When generating RTF, under the heading "File Documentation", subheading
"Data Structures", I see managed output running Microsoft Office 365
ProPlus, but under subheading "Functions" I see good output. I noticed that
the mangled output plaintext includes three consecutive closed curly
brackets "}}}" between bulleted items, but unmangled output plaintext has
"}{/par}}}" in similar context.

I tried editting RTF output by hand to change "Data Structures" section to
match "Functions" section in this way and saw that formatting looks correct
on my machine.

On 2017-05-18 16:52:54 +0000, albert wrote:

Can you please attach a (small) self-contained example (source+config file
in a tar or zip) that allows us to reproduce the problem?

Furthermore also specify the doxygen function you used.

On 2017-05-19 16:47:22 +0000, albert wrote:

Furthermore also specify the doxygen function you used.
should read:
Furthermore also specify the doxygen version you used.

On 2017-08-26 16:56:39 +0000, albert wrote:

From the description it look like a similar problem to bug_784281 (pull
request 596 on doxygen github)

Please verify and otherwise:
Can you please attach a (small) self-contained example (source+config file
in a tar or zip) that allows us to reproduce the problem?

Furthermore also specify the doxygen version you used.

On 2018-05-28 13:13:24 +0000, albert wrote:

I've just pushed a proposed patch to github (pull request 746,
https://github.com/doxygen/doxygen/pull/746).

On 2018-06-10 10:04:53 +0000, albert wrote:

Code has been integrated in master on github.

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.8.15.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).