Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicitly specified <PRE> tags are no longer handled properly (Origin: bugzilla #678177) #4753

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-06-15 15:40:48 +0000, Bruce Florman wrote:

Created attachment 216530
Zipped source, cfg and output from both 1.7.6.1 and 1.8.1.1

I recently switched from version 1.7.6.1 to 1.8.1.1 in order to get the fix for a header guard problem that was affecting one of my modules. Unfortunately, the newer version has now broken the documentation of several other things which used the HTML

 and 
tags to embed "ASCII" graphics in the documentation.

I'm attaching a much trimmed example and the output produced by both versions. While processing the source, version 1.7.6.1 is entirely happy, but version 1.8.1.1 outputs the following two warnings:

X:/test.cpp:253: warning: found at different nesting level (5) than expected (2)
X:/test.cpp:469: warning: end of comment block while expecting command

It's pretty clear that the text between the

 and 
tags is being processed by the newer version of Doxygen, while it was always just copied verbatim by the older version.

I've downloaded and tested the 1.8.0 and 1.8.1 versions too, and both of them have the same problem.

On 2012-06-17 12:03:49 +0000, Dimitri van Heesch wrote:

I think that in your example you should have used @verbatim..@endverbatim instead of

..
as markup processing is done inside
..
, and you clearly don't want that.

One of the markup processing steps is Markdown (which you can disabled by setting MARKDOWN_SUPPORT to NO).

Another is that -- is replaced by – and --- by &mdash. I see if I can make this more robust (e.g. disabling it inside

..
).

On 2012-06-17 12:39:58 +0000, Dimitri van Heesch wrote:

I see that I had already disabled Markdown procesinng inside

 blocks except for a small part (lists starting with +), so I'll correct that as well, and then your example should work with or without Markdown processing enabled.

On 2012-07-11 18:06:36 +0000, Dimitri van Heesch wrote:

*** Bug 679756 has been marked as a duplicate of this bug. ***

On 2012-07-12 15:41:57 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1.2. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.