Improve support for code blocks in included markdown files

[AdarshRawat1]

Describe the bug

When a markdown is included in other markdown using \include{doc} "./Secondary.md" Then, the output of code snippets breaks.

Screenshots

• 

• 

Observations

This happens only if there is formatting in the primary markdown - like ( BOLD , Italic ). if we remove the formattings from primary markdown then everything works fine, but we can't avoid using formatting, so I tried few workarounds one of them worked.

i.e. There is a need to handle the formatting edge cases.

Temporary Fix

• This version gives correct output but \code{.c} doesn't work on GitHub Renders, so I have to keep 2 copies of the same code in docs. (One for Doxygen and one for GitHub )

\code{.c}
    struct secondary_struct {
        int a ; 
        int b ; 
    }
\endcode

p.s. I've been on this for quite some time

To Reproduce

Use this Zip - includedocs.zip

Expected behavior

Correctly formatted code snippets

Version

1.12.0 (Windows 11, WSL, Ubuntu)

Additional context

• Related Stack overflow issue

• /includedoc does Not Work as expected #7430

[albert-github]

I've just pushed a proposed patch, pull request #11226

[albert-github]

The problem with the undesired #!/bin/bash in the code section cannot be solved directly by doxygen as shell scripts are not supported by doxygen.

[albert-github]

Code has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release).

[AdarshRawat1]

The problem with the undesired #!/bin/bash in the code section cannot be solved directly by doxygen as shell scripts are not supported by doxygen.

When the bash script is in a normal markdown( primary markdown) then it works, but breaks only for included codes i.e. \include{doc} "./Secondary.md"

• The formatting is not required, if only the output could be a bit presentable.

[albert-github]

@AdarshRawat1

Can you please give an example so we are sure we use the same example / see the same problem:

• Can you please attach a, small, self contained example (source+configuration file in a, compressed, tar or zip file!) that allows us to reproduce the problem? Please don't add external links as they might not be persistent (also references to GitHub repositories are considered non persistent).

and report the warning / an image indicating what is wrong.

[AdarshRawat1]

@albert-github

I had attached the zip in issue description for the initial issue. For bash specifically, kindly use this file - bash.zip

Output when the bash snippet is in the primary markdown file

• 

Output when we use includedocs to add a bash snippet from a secondary markdown file

• 

Temporary fix using \code{} for snippets in secondary file

• 

[albert-github]

In the original example there is nowhere the wording "secondary markdown" so I added at the end of Secondary.md:

### test secondary markdown

\include{doc} "./Bash.md"

With doxygen 1.12.0 I got:

and with the current master (1.13.0 (b815717)):

This looks OK, otherwise:

• Can you please attach a, small, self contained example (source+configuration file in a, compressed, tar or zip file!) that allows us to reproduce the problem? Please don't add external links as they might not be persistent (also references to GitHub repositories are considered non persistent).

[AdarshRawat1]

Thank you @albert-github this looks great.
p.s. I'll test this locally soon.

Edit:
It works perfectly thanks Albert, for the patch.

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.13.0.
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).