Bug #1800 - edit_xml reformats unrelated parts of the edited file

The standard behavior for an XML parser is to normalize the new lines within the attribute
list before/during parsing. Updated the documentation to advise users to consider this
behavior when using the edit_xml promise types.
Enterprise version updates for EvalContextVariablePut
Fix enterprise stub signature for RegisterLiteralServerData
cfengine.el: minor word constituent fix
Merge pull request #450 from shaunamarie/bug1800-xml-whitespace

Bug #1800 - edit_xml reformats unrelated parts of the edited file
Do not FatalError out of double conversion, remove CF_NODOUBLE magic number
Do not ReportError in PromiseTypeAppendPromise

Handle as ProgrammingError and yyerror in parser.
Remove two consecutive equal if-statements in FnCallIRange
Do not ReportError out of FnCallRRange, return FNCALL_FAILURE
Do not ReportError on lvals exceeding max length, use CfOut and continue
Remove ReportError calls from PromiseTypeAppendPromise, use PromiseCheck
Remove almost useless (and certainly misplaced) call to ReportError in ArgTemplate.

We need arity checks for block and function calls at the parser level,
but this is pending some uniform way of parsing call expressions.
Remove ReportError
Remove global flag PARSING
Added syntax coloring definition for TextPad.
Merge pull request #455 from jstuyts/master

contrib/textpad: Addition of TextPad syntax coloring definition
Replace occurences of Nova -> CFEngine Enterprise in verbose output and error messages
Remove formatting in verbose message
Fix message grammar
and uniform messages
Convert unhandled switch value errors from FatalError to ProgrammingError