updated astcreator version to 1.6.2 in the AST
code cleanup
upgraded AST creator version 1.6.3
Merge branch 'origin/test'
* close #207 unable to reproduce. tested with alarmsl on windows x64
* close #195 unable to reproduce
* issue #194 is still present here
* close #193 problem is not present. it is true that error markers is not present on the working set, but thats not what the issue is about.
* confirmed issue #190
* close #184 is fixed
* confirmed issue #154 is does not override the file but completes with no info
* confirmed issue #132
* confirmed issue #7
* confirmed issue #12
* issue #34 this works with æøå but these are in UTF-8 and present in the charset cp1252 - this is not the same for JP chars
* confirmed issue #53
* confirmed issue #63 no coverage is hightlighted neighter green or red
* close #113 this now reports Operation returns void value. Actual: (() | bool) Expected: bool
* close #188 this is no longer the case the error is shown at the correct line
confirmed issue #96 we could look into the type of console we use and see if it can have a tool bar command attatched linked to the debug target/launch to obtain the IProcess
corrected name compare in TestRunner the compare comapred a lexname with a string.
changed prob repos to point to a release version of prob
resolves #143 the \\ escaping was done after double and single quotes were escaped doubling the number of slashed.
fixed #154 the file creation page was not correctly configure before display
This fixes #96 but unfortunally it uses internal eclipse classes. There were no way to reuse the standard implementation for this so it is a copy with modifications. Maybe Eclipse will provide a better interface for this in the future.
fixed #63 - the problem was that the charset wasnt used while reading the specification files into a string. This string was then parsed with the right charset resulting in parser errors
added null check for iprocess in terminate console action. The process is only ever null if remote debug is used.
close #118

The implementation has been changed such that external files (doc,docx/odt) now use the buildin html coverage feature which generates a web page per file.
modified converagewrite to re-init the properties such that tab stops are restored.

This closes #108 by letting the user set the tab stops in the launc configuration under debugger->parser_tabstop the default value is 1 as used in eclipse. It may be better to stop using tab/detab and just staying with tabs. Eclipse, Word and latex should be able to specify the size of a tab stop.