regression, Unescaped percent sign in doxygen output (Origin: bugzilla #762982)

[doxygen]

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

On 2016-03-02 12:29:42 +0000, Than Ngo wrote:

Description of problem:
there's a problem to build documentation for the apron package in fedora 24. With doxygen 1.8.10, documentation for a certain operator% looks like this:

\subsubsection[{operator%(const texpr1+::builder &a, const texpr1+::builder &b)}]{\setlength{\rightskip}{0pt plus 5cm}texpr1+::builder operator% (
\begin{DoxyParamCaption}
\item[{const texpr1+::builder &}]{a, }
\item[{const texpr1+::builder &}]{b}
\end{DoxyParamCaption}

That works fine. However, with 1.8.11, this is produced:

\subsubsection[{\texorpdfstring{operator%(const texpr1+::builder &a, const texpr1+::builder &b)}{operator%(const texpr1::builder &a, const texpr1::builder &b)}}]{\setlength{\rightskip}{0pt plus 5cm}texpr1+::builder operator% (
\begin{DoxyParamCaption}
\item[{const texpr1+::builder &}]{a, }
\item[{const texpr1+::builder &}]{b}
\end{DoxyParamCaption}

The unescaped percent sign in the second argument to \texorpdfstring turns the rest of the line into a comment, leading to a LaTeX error.

Version-Release number of selected component (if applicable):
doxygen-1.8.11

How reproducible:
Always

Steps to Reproduce:

1. svn co svn://scm.gforge.inria.fr/svnroot/apron/apron/trunk apron
2. cd apron
3. make && make doc

Actual results:
Runaway argument?
{\texorpdfstring {operator%(const texpr0+::builder &a, const texpr\ETC.
! Paragraph ended before @SecT was complete.

\par
l.1954

?
! Emergency stop.

\par
l.1954

! ==> Fatal error occurred, no output PDF file produced!

Expected results:
Successful build of the documentation.

On 2016-03-02 17:57:27 +0000, albert wrote:

Does this problem also occur with version 1.8.11 or the current github version?

Otherwise:
Can you please attach a (small) self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?

On 2016-03-03 09:38:36 +0000, Than Ngo wrote:

i haven't tried the current github version, i will try it today and report the result.

This problem occurs with the stable release 1.8.11, but not with 1.8.10.

sure, i will upload the testcase for this issue today.
Thanks

On 2016-03-05 19:40:22 +0000, albert wrote:

I've just pushed a proposed patch, as the second part of the patch for bug 763104, to github (pull request 454)

On 2016-03-06 13:57:08 +0000, Than Ngo wrote:

Ablert, i confirmed the fix. This issue is gone with your patch.
Thanks!

On 2016-03-06 14:01:11 +0000, albert wrote:

I've set this issue to REOPENED again, not that there is a problem with the code but the issue has not been integrated in the main branch of doxygen yet and afterwards this will set to ASSIGNED so it will not get lost in the further process.

On 2016-03-08 18:38:59 +0000, albert wrote:

As written before (this time I can choose NEW):
I've set this issue to NEW again, not that there is a problem with the code but the issue has not been integrated in the main branch of doxygen yet and afterwards this will set to ASSIGNED so it will not get lost in the further process.

The code has not yet been integrated in the main branch not doxygen.

On 2016-03-13 10:17:32 +0000, albert wrote:

Proposed patch code has been integrated in master branch on github

On 2016-05-05 13:12:55 +0000, albert wrote:

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

On 2016-09-05 13:46:27 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).