The recognition of the type (free or fixed) of Fortran code is not reliable possible. A well known possibility as used with compilers as well is to specify the type of code by means of the extension.
With EXTENSION_MAPPING it is possible to select the type of Fortran code, when not explicitly set doxygen tries to guess the type of Fortran code.

util/patternMatch: don't extract a QCString(QFileInfo) each time we QReg...

patternMatch iterates over the pattern list, while FileInfo remains
constant.

given this, extract the QCStrings for QFileInfo outside of the
iterating loop.
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>

Fix typos in russian translation

Give message when PROJECT_LOGO cannot be found or cannot be converted

Showing error message on windows in case of an error on startup

sqlite3: speedup the SELECTs

Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>

The uniqueness of rows is maintained by first doing a select.
In case the item is not found, it's INSERTed.

This is done for files, refids, params and includes, data
that is not unique by itself, like cross-references for example.
In other words, you can have many memberdefs in one file,
but you can only have one cross-reference between two functions
since the reference location is unique.

So, when SELECTing files and refids, use the file name and refids
as primary key since that's the fastest way to do it.

Also 'OR REPLACE' not necessary in 'INSERT OR REPLACE'.
Signed-off-by: Adrian Negreanu <adrian.m.negreanu@intel.com>

In case the project logo does not exist or cannot be converted give a message instead of a white box.
Also update STR_PROJECT_LOGO in case a filename is selected that cannot be found.

include remained for debug session.

On case, on windows, more than 1 argument is given doxywizard stops without showing a message even though a printf is present.
In this patch the message is show (for all platforms) by means of a message box, furthermore in case the argument --help is given the usage message is given in a message box.

Corrected some definitions for some Fortran keywords

Bug 674851 - Percent to prevent auto-linking in page title is not removed for navpath

Bug 724241 - Internal inconsistency: namespace in IDL

Library was missing in the list of namespaces. In scanner.l constants, module and library are handled in the same way. In namespace.{h,cpp} only constants and module were handled, now also library is handled in a similar way.

remove the % sign from some relevant places. The % sign is to prevent automatic linking.

Pull out property names in Objective-C.

Properly escape the XCODE path.

Made documentation more consistent

Command \< and \> are not properly shown in section headers (and consequently in index)

Superfluous backslash in documentation

A new files have been added but is not incorporated in the windows build part

Place where dot executable is found

Property names are everything after the ::.

This was causing problems on my system where Xcode is installed at
/Applications/Xcode 5.0/

Made documentation for custom commands more consistent and remove not required backslashes

In the pdf version of the doxygen manual (version 1.8.6) the commands \< and \> are shown as < and >
Tests (on the doxygen manual) revealed that the exception rules were nor required.

Some superfluous backslashes were found in the documentation (1.8.6 manual page 52, diagrams section)

The build references for htmlentity.{cpp,h} were missing for windows builds

In the current vhdl part of the code it is required that the dot executable is in the path. On in dot.cpp the possibility exists that the dot executable is found through the configuration setting DOT_PATH.
This patch makes this more consistent