Code highlighting does not account for unparsed case

[gmarull]

It looks like additions made in #760 don't account for the unparsed case:

 \code{.unparsed}
  Show this as-is please
  \endcode

Pygments highlighter doesn't support this language, and so it ends up generating a warning during build process.

[2bndy5]

well, I guess we could add a specific case for this language (never heard of a file extension called .unparsed), but my first impression is that it is more of an issue with pygments.

If you don't want syntax highlighting, then you should use \code(.txt}.

There might be a chance that pygments could guess that the syntax is CMake script, but I doubt that would be a problem because breathe tells pygments what lexer to use (via pygments API) when doxygen's \code block is provided a filename arg.

[2bndy5]

oh! I just found this in the doxygen manual

If the contents of the code block are in a language that doxygen cannot parse, doxygen will just show the output as-is. You can make this explicit using .unparsed, or by giving some other extension that doxygen doesn't support

Looks like we should add this special case due to doxygen's limited syntax highlighting. I still think, that using .txt is more acceptable than something specific to doxygen because doygen doesn't support a .txt extension within doxygen's list of supported language parsers.

[gmarull]

I think breathe really needs to support Doxygen syntax, that is, ignore syntax highlight for the .unparsed case. Otherwise, breathe is really breaking Doxygen compatibility.

[2bndy5]

I'm already looking into a solution that does just that. Seems there was some more changes pushed to that PR that I didn't track...

[2bndy5]

I submitted a patch for this.

@gmarull Thank you again for commenting on the appropriate PR. I'm not a maintaining member, so I'm not subscribed to all breathe-related notifications.