Change-Id: Ibdbad2f8b5471698337fb7838dadd6188b1add7d

Could use a checkbox instead of listbox here, since our LB has only
2 values, but with listbox it'll be easier to add more fill types in
the future

Change-Id: I67cd94b9b49b06434e4a22788b032425c3728e7f

Change-Id: I4f96972255ca99debd53d4302073d1823cc27492

Change-Id: I5078e0e4df18d0aece3240dc537504c11cd623de

Change-Id: I37a0003ca321ca788f7885eb9fdea69ed388a35d

Change-Id: I2e7528cb374d621f148d559c51521013bba62477

Change-Id: Ie96cf3043b126577087eadae5900489a5eb84bcf

OutputDevice::getFallbackFont requires mpGraphics to be created/initialized.
Without the check and initialization OutputDevice::getFallbackFont will segfault.

Change-Id: I18225a24a6767933c8f1ff8f1cfd392543a95132
Reviewed-on: https://gerrit.libreoffice.org/14287Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Use buttons "Add Decimal Place" or "Delete Decimal Place" to change the
number of significant digits with scientific format (also works for
"General" format)
Improve format management for "red for negative"
to be compatible with tdf#88999

Change-Id: Id681afc4fc73674c9823172c6cd71925e63b867f
Reviewed-on: https://gerrit.libreoffice.org/14264Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Scientific format was excluded from being able to increase/decrease
number of decimals, red for negative or thousand separator in UI Format >
Cells > Numbers and Sidebar > Number Format

Change-Id: I56b175a26fc5ba46b9964390f9c098d5d93c73dc
Reviewed-on: https://gerrit.libreoffice.org/14293Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

As part of commit 'fdo#82259 we don't actually care about the ttf version here'
the font data table pointer was incremented presumably to skip
the version number. This results in reading past the end of the array, confirmed by DrMemory.

There is no need in changing the pointer as the parsing is done using absolute offsets.
Furthermore, by moving the pointer, the parser reads incorrect fields (everything shifted 4 bytes).

However, moving the pointer had the desired side-effect (at least on Windows)
that the hints on the right side of most of the fonts were gone
for most cases (the purpose of fdo#82259).

It seems that this was accidental and not the proper fix to that issue.
This patch does make most of the hints show up again on win, and I don't have a mac
to verify if the fonts with the nonsensical hint texts still suffer the issue in fdo#82259.

Change-Id: Idf3bfa292fa063fa05e0ff62920a6bdfa4c94647
Reviewed-on: https://gerrit.libreoffice.org/14281Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Change-Id: Ib6b4f7d5323ea7e94c7b535c68bb6e0af2c49ffa

Theiry implementations were empty both for iOS (well,
TiledLibreOffice, our iOS test viewer app, anyway) and Android.  Part
of work to make TiledLibreOffice use LibreOffieKit instead of
<touch/touch.h> and the older Writer-specific tiled rendering API.

Change-Id: I602a1ebd58ec2c8d6b2d170d65e157d91e0bf521

Change-Id: I8b185ad37e1db3262c2533c0146e4fe7fb3ef3ea

Change-Id: I37b616b3b509c82551d9690c0313e09063a758bc

Change-Id: I824e977e99e8889e5cb69403feb0f1d5e1d0cc31

...and assumed to be merely performance optimizations (so removing them should
hopefully not break any functionality).

Change-Id: I9f40118f5a4bd1526e0cfbf74715455d543bfd54

Change-Id: I4bd2cf8a920c119d508e3316107fa2a616472ba2
Reviewed-on: https://gerrit.libreoffice.org/14259Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

DrMemory reports unaddressable write of 2 bytes (a single unicode character)
in GetClipboardFormatNameW.

While the API documentation do not imply that the buffer length excludes
the null terminator, the returned length does.
Even though in my case the format name was "HTML Format" which is
far shorter than the 256 character buffer size, DrMemory consistently
cought unaddressable write at the end of the buffer.

It's not clear why GetClipboardFormatNameW would need to access
beyond the length of the data it writes, but this fix is harmless
and at least will silence DrMemory, if not fix a genuine issue.

Change-Id: Ib8ac69a65d4fcff53e71f56f9a06c9c7299be1ba
Reviewed-on: https://gerrit.libreoffice.org/14286Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: I08206b7a185a133c18dbb7a09985e3a94736c1e9

Change-Id: Iab76060952ae8c1b64d3ff32e5ae8f5212e016b0
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>

Change-Id: I4ac5fe6f42b425ee96124b2dde39ff397a081638

Change-Id: I50bb5d47c5f430818237308a691306dc097d245e

Change-Id: I2d4f2c1049302eb488e2c6ef3a7142c42c7cb8e9

Change-Id: If33260b5e8af360fba7dd2da296b8b73fc9db654

Change-Id: I0130c70a281e1ea6a82aa4f41be4b4f0b473a958

Change-Id: I64632ecaab720c9c8d6be0b597b990b55682f296

Change-Id: Ie48cf7f89c8c826e56409c2493e1e1250086f10a

Probably most users have no idea what an RSID is, try to describe it
instead.

Change-Id: I60e9d3729c55646b7877411614346b75e7e2c8d2

It was there for a long time. Not a fatal error.

Change-Id: I7804de7494ad027eac6434a542ae55f8d42953e9

Change-Id: If584cf49dc5e8864eca733fd99c04cdb4da0da09

The lcl_TimeToDouble function produced very small numbers that round to
zero.
(regression from 9830fd36)

Change-Id: I091da9c2a913fae0c2bbf229942db3c1bd3598f4
Reviewed-on: https://gerrit.libreoffice.org/14282Reviewed-by: Lionel Elie Mamane <lionel@mamane.lu>
Tested-by: Lionel Elie Mamane <lionel@mamane.lu>

Change-Id: Ic9480340e2a9255aae6d0f97e180e3e68cf97e42

Change-Id: Id8d90569c079a753314ba88b419de9a08b0b6a8b

Change-Id: I40c0f00af941d0aa25e99bdd772b1ac4258cddd6

Change-Id: I5ac6fd2507bda0c985abb54e2269563ed79afc6a

Change-Id: I0acb3209c4ed22088911bcade4c4f20f957294e7

Using the DPI from Application::GetDefaultDevice() is a much better
idea, especially that now oox::GraphicHelper::GraphicHelper() and
oox::drawingml::DrawingML::WriteSrcRect() are in sync.

Should fix the testCropPixel() failure in CppunitTest_sw_ooxmlexport
that appears on HiDPI systems.

Also, fix all the rounding problems that now became visible when the DPI
is the same for both import and export.

Change-Id: Iceb34a8a5a1eaa8ce0824491521ad6b4d2f6949c
Reviewed-on: https://gerrit.libreoffice.org/14280Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: I44eb0d4ecde55cb9c29c39782488e673c8b582e9

I don't see the error outside of the unit test

Change-Id: I56f3d757c4b78e04a3cd340d54612f0b33537a73