Treat the first space text character after a text:tab as significant whitespace

A space character is considered significant when it follows either a
non-space character element (e.g., text:tab), or a non-space character.

From the ODF specs (6.1.3, <text:s/>):
This element shall be used to represent the second and all following
“ “ (U+0020, SPACE) characters in a sequence of “ “ (U+0020, SPACE)
characters.
Merge pull request #203 from peitschie/insert-space-tab

Treat the first space text character after a text:tab as significant whitespace
Synchronize runjslint with current jslint version.
Update JSLint and adapt patch.
Update Closure compiler and more typechecking.
The type Runtime.ByteArray is removed. Uint8Array is used instead.
The more rigorous type checking is enabled by the flag --jscomp_error reportUnknownTypes.
To compile with this flag, build the target typecheck-target.
Revert CC for now.
More type fixes.

This patch also contains quite some cleanups and reorganization in runtime.js.
Fix loading of files via XHR.
Fix pointer to parent class.
Do not forget to set the value of sharedRange.
Add fallback for loading in IE.
Pass Uint8Array directly into Buffer constructor.
Reorder the var sections to be more readable.
Vars without initialization come first on one line, then each initialized var is a separate line.
Document the reason for the casts in containsNode and simplify to assume the standardized version.
JSON is just text, no need to make a binary.
Add more type checking for the IE workaround code.