New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bogus warning: citelist: Unexpected new line character (Origin: bugzilla #742151) #5698

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2014-12-31 13:19:28 +0000, Роман �он�енко wrote:

How to reproduce:

  1. Download the .bib file from here: http://dblp.uni-trier.de/rec/bibtex/conf/cvpr/BenensonMTG12

  2. Create test.dox with the following contents:

/**

\mainpage Main

\cite DBLP:conf/cvpr/BenensonMTG12

*/

  1. Create a default Doxyfile and set CITE_BIB_FILES to BenensonMTG12.bib.

  2. Run "doxygen Doxyfile". It will print a warning:

citelist:4: warning: Unexpected new line character

I believe the cause of this warning is that the regexes in doctokenizer.l disallow newlines within HTML comments. Since HTML comments are, in fact, multiline, I propose the attached patch (which does fix the warning).

On 2014-12-31 13:21:20 +0000, Роман �он�енко wrote:

Created attachment 293519
Proposed patch

On 2015-01-04 09:39:52 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next GIT update.

On 2015-01-04 13:19:39 +0000, Dimitri van Heesch wrote:

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

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment