The old way was that an error cell was evaulated as having a value of 0.
The error cell also showed up as blank in the popup.  Using the error
string is much more intuitive (and some users apparently want this
behavior).

We were supported to convert XML chart data range representations
with a hard-coded ';' as the range union operators, but incorrectly
using UI configurable range separators.  This caused charts with
series that consisted of multiple ranges to be imported correctly in
locales where the range separator (which re-uses the function argument
separator) was something other than ';'.

BTW I plan to remove this "always use Calc A1 syntax" restriction in
future versions.

This reverts commit 694627b7.

This reverts commit fb46e93e.

This reverts commit 58844404.

This reverts commit 0189e888.

During Paint() in ScMultiTextWnd::InitEditEngine(),
ScTabViewShell::GetActiveViewShell() may return a view shell that does not
correspond with the document to be repainted if another document was opened or
when switching between documents. Prevent creating an EditEngine with wrong
SfxItemPool.

it is not valid to use (type & ND_TEXTNODE) before casting to SwTxtNode,
type of SwCntntNode has the ND_TEXTNODE bit as well, but SwCntntNode is not
derived from SwTxtNode.

>>= operator overload turn the right-value of the operator into a
left value... which confuse the heck out of the compiler's detection
of use of unitialized variables (and also C-reader like me for
whom >>= means something else altogether...
(why on earth are we right-bitshifting... with an unitialized variable...
oh! fracking operator overload!!!)