>> In our existing tutorial containing a lot of hand-crafted html, various
>> terms are highlighted by using html tags such as <tt>word</tt>.
>> ... we are trying to replace as many of the non-essential html tags
>> with doxygen commands. This simply makes the source text so much easier
>> to read, and edit. Therefore we have been converting to use \c word or
>> \p word for highlighting.
> You do not need to replace HTML style formating like like
> "<tt>word</tt>" to doxygen style like "\c word". Doxygen understands the
> "<tt>word</tt>" HTML style and several other HTML things. See here:
I'm sorry, but I think you have misunderstood what I was trying to say.
I know that I don't *need* to replace them and I *could* use the html
tags. In fact, the \c command explanation from the Special Commands
page http://www.stack.nl/~dimitri/doxygen/commands.html even says that
you have to use <tt>for multiple word</tt> formatting. I can live
with the html tags if I have to, but I would prefer that they were the
exception rather than the rule.. Having <tt>html</tt> tags in the source
text is not as readable as the equivalent \c doxygen commands. I would
like the source text to be as easy to read and edit as possible too.
The \c command seems to handle \c draw(this,that) and \c filename.h
and \c '&' and \c '->' without problems, and they have "non-word"
characters in them. But in the generated html file \c .h and \c .cxx
appear as plain old .h and .cxx in normal text.
That was the point that I was trying to make.