Change-Id: I2e8214297d071857205c1031b64842e731ef1248

There is a new module cross_tail_build that serves the same purpose for
the build side of cross-compilation (started from cross_toolset) as
tail_build for the host side.

Change-Id: Ic16bae9a7197a1f31cc2dcf31b16bbac68c3300f

Change-Id: Ic493c2e33767968e5a1c1cced66a88295c694b2b

Change-Id: Ic90495f677dc42c0430492548deaa9f9b10e4d44

Change-Id: I7d5d8e380e12cc66255ddc3ac3f70bab7713f8b6

Change-Id: Ifce4c2a6f0f81a9b206795d915cac6705087c2d1

Also cover all UNO primitive types in isPropertyValueChangeable().

Change-Id: I21a1809ed2a6b58f68ef82252f513991e0f012af

Change-Id: Idbad933cf5e3b297e7131e66202a0250b4c3def8

Change-Id: I7f0d68ee59e7a36254267d652de398cc371c7f8c

Change-Id: Icf8ddddb9a45435968bc43d8bc7a033ce5cfd702

Not all its tests have been converted.  This is work-in-progress.

Change-Id: I90a789852e05a214440e4f87011b6de3d3d4d08a

SwHTMLWrtTable::Write no longer writes BORDER and BORDERCOLOR attributes
on TABLE elements, but instead various CSS "border" properties into STYLE
attributes of the TD elements.  However, it was forgotten to also remove
the ROWS and FRAMES attributes, which (as the comments helpfully explain)
only make sense in case BORDER is actually written, and cause Mozilla to
not render some of the borders in cases RULES=ROWS or RULES=COLS.
(regression from d18feffd)

Change-Id: Idd08fd733670f4410349a45de882710b19a31f67

Change-Id: I753ee58e5999f9ba0da5adeaba7800b76f7f4d68

Change-Id: I6cc92e2242cf0f162b5c670bf2e70f1e8fc49a28

Change-Id: I57463bdcb8f580866d56741c427fd9882a151b07

Change-Id: I9686ed60c31129fc4bacf63fec2d6314bf513c73

Change-Id: I17d404640494c3964bdbada8f855af6e97823c2d

The STYLE attributes on TD elements (except for the first) start with a
spurious semicolon, because the bFirstCSS1Prop variable is not reset.
Apparently the semicolon is a separator in STYLE attributes, so it is
probably invalid to write a spurious one, but Mozilla can still render
the borders right, so add a workaround to CSS1Parser::ParseStyleOption
to skip initial semicolons.
Fix the export by using the SwCSS1OutMode to set the mode (also turning
on encoding while at it), which is the only way to reset bFirstCSS1Prop.
(regression from d18feffd)

For TD elements, the SYLE attribute containing "border" properties is
read, but the borders end up not at the table cell, but on some span or
paragraph inside the cell.  So insert a special case that re-routes
the SvxBoxItems containing the borders to FixFrameFmt, where the
properties set at the TD element directly now override the SvxBoxItem
that is derived from BORDER etc. attributes of the table.
(regression from d18feffd,
 which changed the way the border attributes are written)

g_source_get_current_time has been deprecated since version 2.28 and should not
be used in newly-written code. ... This function ignores source and is
otherwise the same as g_get_current_time()

not using g_source_get_time seeing as our baseline isn't there yet

Change-Id: I9f389cbb8d23353c0a12eacb215d61256b28f643

Change-Id: I88cfd9592e11aa7dbe704df4810090b6a1ce4c66

Change-Id: Ib6f7e3b4f750e38198c09cdb4bd8ee2b7161ac53

Moved new fixed fraction built-in formats into the fixed set so they keep
their relative key position when switching system locale.

The only code that uses the binary storage format of SvNumberFormatter is the
SvNumberFormatsSupplierServiceObject for the NumberFormatsSupplier service
during streaming of forms' formatted fields with OFormattedFieldWrapper. That
certainly does not need access to files created before the year 2000 ... so
slice off that awful compatibility cruft.

Change-Id: Ib7188a98230345557187b00826f33a2ad39a4f83

Change-Id: I756c0a19bea7b1cc0e290d9f382a04d655819bfb