Supporting linking for methods bound to FORTRAN classes in source definitions

Merge branch 'feature/bug_size_latex' of https://github.com/albert-github/doxygen into albert-github-feature/bug_size_latex

Conflicts:
	src/doctokenizer.h
	src/latexgen.cpp

Add source code possibility for RTF output

Convert FORTRAN modules to namespaces

Fixed typos in C/C++ comments. There are no functional changes.

fix docbookgen.cpp to support other than english

    1. support other than english
    2. fix broken example link id
    3. fix incomplete TOC : no Classe etc.
    4. add brief description for Functions etc.
    5. Comply with REPEAT_BRIEF
    6. Do not output duplicated contents when detailed descripton is missing.
    7. set table colwidth for Param/RetVal

Bug 722940 - classes with same name in different namespace adding to same group

Fixed typos in comments. No functional changes.

Fortran color CALL as keyword

Fortran code color END (regression pull request 259)

This is a regression on pull request 259.
Fortran code like:
      end if
was not colored properly anymore. This has been corrected with this patch.

Analogous to Latex and HTML output the possibility to have source code shown in RTF output is created.
Based on question: http://doxygen.10944.n7.nabble.com/RTF-lack-of-source-code-tc6936.html

Color the word CALL as keyword.

If two classes with the same name, but in different namespaces (so different qualified names) were added to the same group, only one of them would end up in the group.
The problem is caused by qualifiedName of the class not containing the qualified name but the class name when a class is added to the group.
A workaround is to use the name attribute of the class, which does contain the qualified name.

Bug 687576 - Add support for LATEX_EXTRA_STYLESHEET

Extra empty line in source fragments

Support for INLINE_SOURCES in Fortran

Fortran continuation character seen as begin of function call

Fortran color code of END

The color for the single END in Fortran code was of the color of the flow type entities though for all the flow entities the entity name is mandatory. For the entity statements of some keywords e.g. SUBROUTINE and FUNCTION the entity name is not mandatory with the END statement. The color of the single END statement has been changed from the flow type to the normal keyword type.

In case in fixed format code a line like:
"     x   ( " existed and the x was on position 6 the "x   (" was seen as the start of a function call.

Fortran does not yet support the INLINE_SOURCES, with this patch (part of) this omission is solved.

In case of a language that does not uses curly brackets to define blocks (such as Fortran) there was a newline character in the variable c and this was written in the "code fragment" buffer and subsequently written to the output resulting in and extra empty line on top. I languages using curly brackets this is later overwritten by the while loop searching for the open curly bracket.