The current limit for a message length in the messages file is 4095 characters. Most of the time this is more than sufficient, but in case of Fortran and a lot of arguments this might not be sufficient.
With Fortran the "data type" can be quite long as it can also includes words like: double precision, dimension, intent(inout) etc. When we have a lot of arguments and just one is described it also tries to write out the names of the non-described parameter/ arguments with the word parameter prepended resulting in an even longer line.

This patch increases the size of the buffer.

Update dot.cpp: comma added for dot syntax

comma added for dot syntax

Tcl: Bug 729092

Bug 702584 - \cite rejects valid BibTeX keys

Update test 058 because commit 9d315a98 fixes also Bug 729135

Bug 705503 - TCL: Documentation of oo::define is not working

Support more Tcl commands

Added support for C# property accessors visibility modifiers

Added possibility for . (dot) and + (bit analogous to file names. A . (dot) cannot be the last character)

Conflicts:
	src/docbookvisitor.cpp

1. New Feature: Adapted Class Graph generation for DOCBOOK
2. Fixed DOCBOOK Code documentation formatting
3. Fixed Doxygen to handle FULL_PATH_NAMES for DOCBOOK generation

Bug 702584 - \cite rejects valid BibTeX keys

Bug 625601 - FORTRAN: recognition free versus fixed formatted code

Resolves the error of unbalanced tags opened/closed in docbook output

--HG--
extra : rebase_source : aedb08ea08b1b0a983e31a11765c75b56c0b5ceb

--HG--
extra : rebase_source : 71a597ee1427c9ee52d8879ffc360f91912f8561

According to the documentation the .bib is automatically added to the names in the CITE_BIB_FILES. In the example given with this bug this was not the case.
In case CITE_BIB_FILES was set to 'my.bib' it was working, but with only 'my' it wasn't.

Bug 589707 - Flex .rule file for Visual Studio build can't cope with spaces in filenames

Correction in documentation based on comment by dnm on June 19 2014

Adjusted the rules files and where and the vcproj file so it can handle paths with spaces as well.
When generating the documentation (Cygwin) a small problem appeared in a Makefile when there is a space in the path, this is solved as well.

--HG--
extra : rebase_source : f516669986006db5aca6af6417f323e57fa848d1

--HG--
extra : rebase_source : 5d7e3a2b3c549419c672cddd8d780542053d68bb

resolves the error of unbalanced tags opened/closed in docbook output: parser error : Opening and ending tag mismatch: para line 358 and tbody

Tcl: collect XRefs also if INLINE_SOURCES = no