Bug 687576 - Add support for LATEX_EXTRA_STYLESHEET

Added the possibility for  LATEX_EXTRA_STYLESHEET analogous to  HTML_EXTRA_STYLESHEET. Special attention has been paid to the extension as ".sty" is automatically added by the \usepackage
Removed some comment statements.
Extra empty line in source fragments

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.
Support for INLINE_SOURCES in Fortran

Fortran does not yet support the INLINE_SOURCES, with this patch (part of) this omission is solved.
Fortran continuation character seen as begin of function call

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 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.
Merge pull request #259 from albert-github/feature/bug_end_code_color

Fortran color code of END
Merge pull request #258 from albert-github/feature/bug_fortran_source_continuation

Fortran continuation character seen as begin of function call
Merge pull request #257 from albert-github/feature/bug_fortran_inline

Support for INLINE_SOURCES in Fortran
Merge pull request #256 from albert-github/feature/bug_first_line_inline

Extra empty line in source fragments
Merge pull request #253 from albert-github/feature/bug_687576

Bug 687576 - Add support for LATEX_EXTRA_STYLESHEET
Fixed typos in comments. No functional changes.
Bug 722940 - classes with same name in different namespace adding to same group

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.
Fortran color CALL as keyword

Color the word 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.
Merge pull request #265 from albert-github/feature/bug_ftn_end_color_regr_259

Fortran code color END (regression pull request 259)
Merge pull request #263 from albert-github/feature/bug_fortran_call_color

Fortran color CALL as keyword
Merge pull request #262 from orbitcowboy/master

Fixed typos in comments. No functional changes.
Merge pull request #261 from lhelsloot/feature/bug_722940

Bug 722940 - classes with same name in different namespace adding to same group
Fixed typos in C/C++ comments. There are no functional changes.