Change-Id: I06dde63093eab4e5e1c692f6363aca70b89de96a

The problematic path was "m,l21600,r,21600l,21600xem@1@0l@3@2nfe", here
"m,l" means an implicit "m0,0l", but only the first zero is in the
coords list. If the second is missing, assume 0 as well.

Change-Id: I03065e34c959103c9caf64271aa3ebbb7ad52726

Change-Id: I782942e25107ce996f3f31c3f53123c118d81838

Change-Id: Ibe8e80169b222e425df7016a0012591793546adf

Change-Id: Ia30628e093a885165b2d8a7b1a999c0dc7ee65cd

Change-Id: Ic9ea40c430e0b0ab0d46bac3ba150ddac96c6acc

Change-Id: I3dcbc1b643a29ee080e5b034dccd4882a43590a4

Passing an, as such useful, verbose error message to the
CannotActivateFactoryException constructor is fairly pointless if that
exception ends up being unexpected and causes program
termination. Which of course is exactly the case when one would be
very interested in seeing any message associated with the exception.

Change-Id: I1cd987669e39e47d5f072690dc5013e4a42fd50a

aStr may be 1 larger than pKernArray.
Trivial fix by checking the largest index; not sure if it would be a
good idea to allocate pKernArray with the larger size in the first
place, but that would be a bigger change...
(regression from 02ce7344)

Change-Id: Ia33feab001c34e85066b7596d8873f41588984e9

MarkDataChanged() is quite expensive & in theory unnecessary when no
selection is present.

Change-Id: I6967b914735462403a77568010532b37a1d8f333

Change-Id: I38b91f9e02c1addd8a0ef427b7b09cdf1a04ee95

This is a leftover from the 1 million row conversion we did years ago.

Change-Id: Ib50819ed51c7017bcc559bfc8b6062ff46615d09

Add more unit tests, reduce the number of rows that we know are empty
that we iterate over while saving by shrinking the column set that
we scan as we go along.

Change-Id: Iebd817d9a8a01fa6abeaa24c4aace92233313e0f

boost::optional appears to show up rather heavily on many profiles.
We already use mnElementToken == DONTKNOW to flag / use these guys.

Change-Id: Ibf2b0167f259cc601da2fb9703e880b78e60886e

Change-Id: I4cec5ba61762ac87d5bfb07b15ab661955e207ac

...there was a handful of Hide(true) calls, which would happen to actually mean

  Show(false, SHOW_NOPARENTUPDATE)

but I assume those were typos rather than genuine requests for
SHOW_NOPARENTUPDATE.

Change-Id: I20310d58437bb556f95965885f82784f855b517d

Change-Id: Ib74830671694f2c78adc7a11296971a7edd2f781

so we can safely change the return of 0xFFFF to 0 without
changing any callers. Which makes this safe seeing as before
now every caller would have done something stupid with the
results

Change-Id: I10d9f12525de10661ed82f3405e6c728d38be106

Change-Id: I93309674ef50e8ca7438874378fb01484bb7f9f3

Change-Id: Icc9def55a814fc1309ce143a84effc140a90a92b

It's the isCustom field that should be checked to see whether the
customAttribute field has been assigned or not.

Change-Id: I5d2af26b675ab0cbc0e1844eb98ebaf5145eb73d

Change-Id: Id816d1da328e83197e0b1b4641ed894b62f1c78b

Regression introduced with 8fde2885
Crash happened under ScExternalRefManager::maybeLinkExternalFile()
pLinkMgr->InsertFileLink(). ScDocument::GetLinkManager() introduced
GetDocLinkManager().getLinkManager(bAutoCalc) leading to the LinkManager
being created only if bAutoCalc is set, which may not be the case during
file import. Changed to unconditionally create the LinkManager again so
the link can actually be inserted. Whatever the intention was, that
needs rework.

Change-Id: I2ae66ac7f62c3cfd92c5bf1a147feb06b0155275

Change-Id: I6c740c8b2634785e794704ce0f2d89878e01ac51

Change-Id: Ica71b7c2bc31a211cccbb473071d1c4c82f4a4f4

Change-Id: I720b921367ad810e3d775155535c1e05ab5f6f2c

Change-Id: Id10a0d7e0d635a6829966dc5ce0110dc715d7c6c

Change-Id: I49621bc3887baf8fcee17559818193325b83f27d

Change-Id: Iff26cd2c966fc747895fbde7229a457a99c62f7a

Change-Id: Iaaca13e732c234e9051be0ab66a7625f9c106eea

Change-Id: Iac6b7a01dd35fb6bb350644235409c4019a0a086

Change-Id: Ib33b2a36e7fcd96ca9e5deff19e1d2d18aebd012

Change-Id: I9ffdabdc44677033d8c8ac1b025ccb7c600db664

Change-Id: I89799855925b7c246262ae56c2637e20e51cffee

... i.e., from 16.16 FixedPoint with default value 0x00010000 to percentage.  At
least that is what I assume the odd code that looked like that since its
inception in f90ea740 "INTEGRATION: CWS sj09"
was acutally supposed to do.

Change-Id: I482fb3c1d00757b2f18c587bbb6b4a6755392d2f

Change-Id: Ifd33ea9c1f91865d5ae5175eefa9b65107404bf0

Change-Id: I32b458390130e9ed83af0831069329ac8f672d67

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

This is a unit-test added to complement the patch that added support
for the preservation of 'Track Changes - Paragraph Properties Changed'
from a DOCX file.

Conflicts:
	sw/qa/extras/ooxmlexport/ooxmlexport.cxx
Reviewed on:
	https://gerrit.libreoffice.org/7401

Change-Id: Ic81a5ac9ee369ae0f1d2f8d1a1fe54ea5e6b7402

Change-Id: I5888fb3e1ffa1bfdf9b91c06087ef5b7ccbb82ec