- Fixed highlighting defined type in variable declarations
- Corrected parser state following docBlock closure

Highlighting corrected for case statements without new line (regression)

Coded coloring of flow statements corrected (regression)

Which patch 8e8c9a1e (dd. May 6) the rule:
<Start>{FLOW}/[,( \t\n].*
has been changed into"
<Start>{FLOW}/[,( \t\n]
(analogous: <Start>{COMMANDS}/[,( \t\n])
To overcome the warning: fortrancode.l:744: warning, dangerous trailing context.

The result is that the code coloring of (e.g.) the if statements in:
      subroutine test_on_if
        if (a == b) then
          c = d
        endif
        if(a == b) then
          c = d
        endif
      end subroutine
was removed, due to the fact that the rule: <Start>{ID}{BS}/"(" was used instead of the flow coloring rule.

This patch fixes the rules so the lines are colored again and there is no warning.

Conflicts:
	src/fortrancode.l

Add FORTRAN 2003 keywords and commands

Add class/procedure vardefs to FORTRAN code highlighting

Add import keyword to FORTRAN code highlighting

Missing word after \n command in Doxygen rtf output, version 1.8.5 & up

Make index for faq

After a \par command no space or new line was present resulting in the joining of the \par with the first word after the \n.
Inserting an newline solves this problem

Currently the FAQs are in a numbered list, no index / overview. This patch places the FAQs in paragraphs resulting in a readable overview (in index or with a tableofcontents in HTML

Bug 728654 - configuration stops with settings.h missing

This bug fix fixes, in a general way, a number of issues encountered on Solaris
- configure
  - ! (exclamation mark) not recognized properly, but with mkdir -p no test is necessary
  - sed problem regarding removing last , (comma) in language list. Is automatically replaced in with a space when translating language names to upper case.
- lang_cfg.py
  - corrected check on number of arguments

Bug 623299 - Fortran: quotation after define causes error

For the determination whether the file is free or fixed formatted code just see lines starting with # as comment lines

Made INSTALL file version and date independent

Bug 172072 - $title doesn't work in LateX header

Corrected copyright year

In case $title is used in the latex header or footer it is now replaced with the empty string (it was left inside, resulting in non translatable LaTeX code), the documentation has been updated too.

See also:
Bug 668004 - LATEX_HEADER should share common information with HTML_HEADER
Bug 401327 - LATEX_HEADER: $title does not get expanded