http://lists.freedesktop.org/archives/libreoffice/2011-December/021638.html

It's simply a bunch of documents with various math features in them.
It'd be nice to have an automated test built on top of them that
checks the formula is the same (roughly, in the meaning, it can't be
precise because import adds e.g. extra {}'s) after an export+import
roundtrip.

correct minor css rendering too

When writer would choose the same bias automatically that word
implies or this doc hard-codes, then elide the font-forcing.

Generalized the OSX ppc workaround for ancient bison versions,
factored out for all gcc platforms. Put bison version detection
into configure accordingly, to switch on that, and not on platform.

This patch fixzex bug fdo43586, more room needed for localized strings in named range dialog.

Otherwise we would fail to import the cell contents of those documents
that don't include table styles at all.  Some hand-crafted ods documents
don't provide table styles, which 3.4 imported just fine.

Some parameters don't work with external references, however, such
as PROTECT, PREFIX and WIDTH.

test XDataPilotFieldGrouping::createDateGrouping is broken

Otherwise that method will set #REF! to the cell when it sees the tab
index being -1.  We don't use that index in that code, so it's safe to
do this.

Older releases stored a few function names not defined by ODFF, namely
EASTERSUNDAY instead of ORG.OPENOFFICE.EASTERSUNDAY, TDIST instead of
LEGACY.TDIST and B instead of BINOM.DIST.RANGE.

Since OOo/LibO 3.3 the proper function names can be read, additionally to the
"wrong" names. Now it's time to write the proper names and still accept the
incorrect ones.

Test cases are attached to AOOo issues:
ORG.OPENOFFICE.EASTERSUNDAY
https://issues.apache.org/ooo/show_bug.cgi?id=112882
LEGACY.TDIST and BINOM.DIST.RANGE
https://issues.apache.org/ooo/show_bug.cgi?id=110229
Note that the FALSE in A2 and A3 is a result of the string comparison of the
actual formula, that differs in separators (, vs ;) only.
(cherry picked from commit a9b03bd1)

This is also another unfortunate bug due to the logic change caused
by the DECLARE_LIST removal.  There was one crasher due to out-of-bound
array access, plus one incorrect behavior concerning cell content
placement.  Both are now fixed.