doxygen-develop

[Doxygen-develop] Double dash within <tt> or <code> is again (or still?) broken

[Markus G. <mg...@we...>]

Hi,

This issue has already been reported ten years ago in bugreport
https://bugzilla.gnome.org/show_bug.cgi?id=133418 and was marked
as resolved, however, I see this issue again/still with current
sources from git (just sync'ed my local copy).

Simply try something like
	<tt>--prefix</tt>
or
	<code>--prefix</code>
and you will get '&ndash;' in the HTML output and '--' in LaTeX
(should be '-\/-' to prevent getting the en-dash). Same applies
to the em-dash, though I assume that this is used less often in
<tt>/<code> environments.

On the other hand, the LaTeX output contains an unnecessary italic
correction for dashes between words. For example, 'so-called' is
typeset as 'so-\/called'.

Unfortunately, I couldn't yet figure out where things go wrong.
The output of '-d commentscan' already reports '--' or '&ndash;'
depending on the MARKDOWN_SUPPORT setting, however, the final
output is identical in both cases. Some hint where to start would
be very welcome.

Thanks,
Markus

Re: [Doxygen-develop] Double dash within <tt> or <code> is again (or still?) broken

[Dimitri v. H. <do...@gm...>]

Hi Markus,

A recent change (independent of Markdown) was to treat -- as ndash and --- as mdash.

When MARKDOWN_SUPPORT is enabled you can already do what you want using `--prefix` (i.e. using backticks)
Without markdown support enabled the only way to prevent interpretation is to use \verbatim..\endverbatim,
so this is not very convenient for inline fragments.

I just committed a change to also allow escaping of -- and --- via \-- and \--- so you can also write
<tt>\--prefix</tt>.

Regards,
  Dimitri

On 12 Apr 2014, at 18:49 , Markus Geimer <mg...@we...> wrote:

> Hi,
> 
> This issue has already been reported ten years ago in bugreport
> https://bugzilla.gnome.org/show_bug.cgi?id=133418 and was marked
> as resolved, however, I see this issue again/still with current
> sources from git (just sync'ed my local copy).
> 
> Simply try something like
> 	<tt>--prefix</tt>
> or
> 	<code>--prefix</code>
> and you will get '&ndash;' in the HTML output and '--' in LaTeX
> (should be '-\/-' to prevent getting the en-dash). Same applies
> to the em-dash, though I assume that this is used less often in
> <tt>/<code> environments.
> 
> On the other hand, the LaTeX output contains an unnecessary italic
> correction for dashes between words. For example, 'so-called' is
> typeset as 'so-\/called'.
> 
> Unfortunately, I couldn't yet figure out where things go wrong.
> The output of '-d commentscan' already reports '--' or '&ndash;'
> depending on the MARKDOWN_SUPPORT setting, however, the final
> output is identical in both cases. Some hint where to start would
> be very welcome.
> 
> Thanks,
> Markus
> 
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment 
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Doxygen-develop mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-develop