Conflicts:
	src/libdoxygen.pro.in
	winbuild/Doxygen.vcproj

-  QCString idLanguageCharset()
-  QCString trAlphabeticalList()
-  QCString trDCOPMethods()
-  QCString trDirDependency(const char *)
-  QCString trFuncProtos()
-  QCString trFunctionPrototypeDocumentation()
-  QCString trSearchForIndex()
-  QCString trWrittenBy()

i.e. the ones reported in translator_report.txt as...

======================================================================
WARNING: The following translator methods are declared in the
Translator class but their identifiers do not appear in source files.
The situation should be checked. The .cpp files and .h files excluding
the '*translator*' files in doxygen/src directory were simply searched
for occurrence of the method identifiers:

  QCString idLanguageCharset()
  QCString trAlphabeticalList()
  QCString trDCOPMethods()
  QCString trDirDependency(const char *)
  QCString trFuncProtos()
  QCString trFunctionPrototypeDocumentation()
  QCString trSearchForIndex()
  QCString trWrittenBy()

... winbuild/Doxygen.vcproj removed.

The conversion tables/functions from within translator classes not used
after conversion to UTF-8.

When running... doxygen/doc>py translator.py
This script should be updated. All translators do use UTF-8
internally.  The TranslatorDecoder adapter should be removed
from the code and its usage should not be checked any more.

(I do not believe I ever had so much time to add a check like this
to the translator.py :)

Actually, the translator_je.h and translator_ke.h use only ASCII
characters. The idLanguageCharset() just returns "utf-8" now.
The TranslatorDecoder not used for the translator classes.

This is a (generated) dummy file, that is needed for compiling files
that are generated with flex under Windows 95/NT.

Almost all translators converted to UTF-8

Basically, only "from __future__ import print_function" added.

The mailto.txt file is generated by the translator.py.