When trying to upgrade from doxygen 1.8.10 to 1.8.11 we noticed that doxygen is becoming very confused. It tried to create files with non-printable characters, like character 0x0F.

After some searching, we noticed that in the generation of the globals.xhtml and globals_<firstchar>.xhtml files there was a reference to a .doc file which was part of the code base.

On trying to do something similar with our config, we noticed the same problems with a blank .doc file, though not with a .docx file. Further investigation is still required, though it looks like the files which are picked up by doxygen have been changed between 1.8.10 and 1.8.11. (However I don't find this in the change log)

Most important part of our configuration: (I'll try to update the local configuration, though as generation of documentation takes hours, this takes time)

# If the value of the INPUT tag contains directories, you can use the
# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
# *.h) to filter out the source-files in the directories.
#
# Note that for custom extensions or not directly supported extensions you also
# need to set EXTENSION_MAPPING for the extension otherwise the files are not
# read by doxygen.
#
# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
# *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
# *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f, *.for, *.tcl,
# *.vhd, *.vhdl, *.ucf, *.qsf, *.as and *.js.

FILE_PATTERNS          =