Change-Id: Ia3c6df80ff26ea00e91dd97841c4867bf0a55705

Change-Id: I5dd8dc9a3a256e51706d32249260f6561202bbc9

Change-Id: I08666492fea76395fd24b0ebd02647821f49573d

Change-Id: I7fae615f644158c9e5137330daa4873ad4192fd5

Change-Id: I9d75b0a625009d483467042584d2d2f89501cb96

<sigh> added some files that were part of a patch that I was testing
were not intended as part of commit

Change-Id: I34ed7f55de28fa09739c0dd8d5084824de676477

expand the existing borders import check to cater for xlsx ( and
testing for fine/hair border styles )

Change-Id: Ic5c3cd46e0049dbce9997f0881c4d98e0d64e00c

Change-Id: I79cb4db1ec87258c45ddc786914b32f47e96acf5

Change-Id: I5ec18176291e128c79d3e51e39b8a42b17a27b30

Change-Id: I3a4c16995ac46bbb53923b9c47101826673cdded

FrameworkHelper into SdGlobalResourceContainer

Found by: zhangjf
Patch by: zhangjf
(cherry picked from commit 939e2900)

Change-Id: Ic053c02b02add045e60bac5c7dd7d8e8c2752f0c

This bug fixes the DOCX import and export filters, adds a new property
to the document model and updates the UNO API.
There is no need to add layout \ UI updates, because in Word
the only way to turn this on\off is using a simple button,
and there is no way to control the shading color itself.
However, ODF import \ export filters should be updated in a future
commit.

Conflicts:
	sw/qa/extras/ooxmlexport/ooxmlexport.cxx

Change-Id: I1d34cec79289e38c08e42a4c6265d998e1edfdef
Reviewed-on: https://gerrit.libreoffice.org/4452Reviewed-by: Miklos Vajna <vmiklos@suse.cz>

Change-Id: I846030c5c7ad4e30e5286d1ee30130a397ad4daa

Change-Id: I096742a1849d7fc8310aac8addd18b15cc40fea3

Change-Id: If8c9b4bf1041881bb8fb92c51e2bce22909147c5

Change-Id: I0ab3fabb82c839f5194b0e20eb834dd86635a609

Change-Id: I29967aa15b879cc96cccb686814e594526b200d5

Change-Id: I1cbfa318e75ac5c86c0c7d2dbc033601fec3d46c

Change-Id: I3b87820eee8182e6c4b36d62acfe90cabd830c86

Change-Id: Idec79adce1f4bbb4003b3e8fb76a1f4a40fcc13f

Change-Id: I70f3c31e4b2f44d2b30020a588aaa53d3b63d452
Reviewed-on: https://gerrit.libreoffice.org/4447Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I4cd9841127b1d4a294d7f001b646259c61eb1172
Reviewed-on: https://gerrit.libreoffice.org/4443Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I7a7a77c26b74078f7fc160fbaa1c8d4e912b844e
Reviewed-on: https://gerrit.libreoffice.org/4442Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>

Change-Id: Ib7585036116e8d370d6a689e4d9adae209024e6b

Change-Id: I1337413e1ee49b7d90671ac517dbb2bd918dbebf

Change-Id: I5d88c94a9cf0bbd194c8c505de7cc34bb9e20500

Change-Id: Ia68f49996d4d50142c04d35ef2babb321afc4b3f

Change-Id: Ie5dc6b93fbcd65d7763fb9232a984236fb7bd745

Change-Id: I2f299dd7244e7418959f82f94a56d8cc1749aaba

The underlying multi_type_vector didn't have the concept of position objects
back when the matrix was reworked. It is now available, and there is no reason
why we shouldn't use it to speed things up.

Change-Id: Iac75a5584779c16e6eff7fcd577fc3d717c3c2e7

The new ScHorizontalCellIterator internally uses iterators for each
column to track positions. This means that, if a cell value in the iteration
range chnages while the iteration is on-going, those internal iterators
get invalidated. Allow the client code to rehash the iterators when modifying
a cell content during iteration.

Having said that, it's best not to modify cells during iteration.

Change-Id: Ida453d4f883e1fbcbab4eb0401e37fea8c0b901d

Align the array position of RowInfo by comparing its nRowNo value with
the current row number.

Change-Id: Idd26636cac0ba4ade1b538dd68580b469611da04

Change-Id: Ie8f8c2227b35ffb81f902458ce1b0a732b430b53

Remove CELLINFO macro, and rename nArrX and nArrY to nArrCol and nArrRow.

Change-Id: Id105cfefc44e454be2df96a4084dee9185435fab

nCol and nRow are better than nX and nY etc.

Change-Id: Ie92d4e2727a1100736610a3876721d61e8279b15

Change-Id: I5db7923be8444db8a0cb1a6766f967d731776535

Also, use position() to update the value, to avoid performing position
lookups twice (once for getting the current value, and once for setting
the updated one).

Change-Id: Iaa1575a4938b996266c01c8b3170e6a65b871961

This would cause column cell and text attribute arrays to go out of
sync, because the formula cells may be stored and interpreted in places
such as change track and conditional formatting.

We still need to find a good way to mark text attributes "obsolete" when
formula cells are re-calculated.

Change-Id: Ida612806d3afec23c5ae501f2fc8cc7d52e019a8

Change-Id: Ib7a7abd82060b19f7911f1fef5ccccff5d850055

Change-Id: Id49307f8b7050e1f95cd589421f01a85b4e992b2