After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 605659 - Byte Order Mark of UTF-8 coded sources is parsed too in version 1.6.1
Byte Order Mark of UTF-8 coded sources is parsed too in version 1.6.1
Status: RESOLVED DUPLICATE of bug 602818
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-12-29 12:20 UTC by Roland Fischer
Modified: 2009-12-29 19:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example to reproduce the bug (35.34 KB, application/x-zip-compressed)
2009-12-29 12:20 UTC, Roland Fischer
Details

Description Roland Fischer 2009-12-29 12:20:00 UTC
Created attachment 150532 [details]
Example to reproduce the bug

assume you have UTF-8 coded sourcefiles like visual studio .NET files.

doxygen 1.6.1 generated tagfiles have the first line of a sourcefile parsed as a variable because it doesnt ignore the UTF-8 BOM at the beginning of the file. so it cant i.e. recognize using as a keyword.

However, including tagfiles in other projects seems to be broken. Therefor i cant see what he's doing with it.

important parts of the Configfile:

DOXYFILE_ENCODING      = UTF-8
EXTRACT_ALL            = YES

INPUT_ENCODING         = UTF-8

TAGFILES               = 
GENERATE_TAGFILE       = Tagfile
ALLEXTERNALS           = YES
EXTERNAL_GROUPS        = YES

--------------------------------------------------------------------------
tagfile

<?xml version='1.0' encoding='ISO-8859-1' standalone='yes' ?>
<tagfile>
  <compound kind="file">
    ...
    <member kind="variable">
      <type>using</type>
      <name>System</name>
      <anchorfile>_test1_8cs.html</anchorfile>
      <anchor>a81a223a02c34d82b47199f08308847f2</anchor>
      <arglist></arglist>
    </member>
    ...
</tagfile>
Comment 1 Dimitri van Heesch 2009-12-29 19:28:11 UTC
Should be fixed in the next release

*** This bug has been marked as a duplicate of bug 602818 ***