Change-Id: I4ad28b049de5f7268ee1ca2e8992e2f29ed05380

Change-Id: I90a28e34eb45819e240931cd751ac0a546ea6be8

Change-Id: If17510b572aa172c8d973f74b881b0d723213eef

Change-Id: I3cb377cfa99914fdba00504fb7d955e088bfca76

Change-Id: Iec1d1539db0b44d2ddc420cf500585098d4793fc

Change-Id: I86fab011150be6f151e4fd6a51246f41e86e5833

When there was a redline in a DOCX file that relates to formatting -
the DOCX exporter automatically assumed that if the 'after' properties
contains an 'XML_lang' node - then also the 'before' properties
should also contain the 'XML_lang' node - and this is wrong.

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

The reason for this - is that the function 'WriteCollectedRunProperties'
needs to be used by the redline exporter (to export collected 'redlined'
properties) - and the 'mergeTopMarks' is not needed there.

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

Change-Id: I74122f5a1fb48f9615f7364d3ee5015f0d7e72a6

Change-Id: Idcf6e210a888a80fa4adb7ac8532e4db075eebf7

Change-Id: Ia75ccbe4ffd1e44585a590c7931b920168a6c703

Change-Id: Iaaef26fdb5f1f46b6e0ffece484cf884cc29c84c

Change-Id: Id4d1cab36501a98f136590592471b31ca5043ce4

Change-Id: I407b1f552ce089c0ff1d6bdadc1cc618fb713646

The previous code was doing it only with the first referencing pivot table,
which would break the rest of them sharing the same cache if
the first one doesn't contain all group dimensions used in all of the
referencing pivot tables.

Change-Id: I35d6907ef8db7ed69db42583cac92b2b74406e2c

Also add some flags to change the dumping behavior a little.

Change-Id: I291cdd7d055614b9e7074bdc47292ecd41a474ac

Because the new implementation relies on the visiblity flag of the
dimension members, they need to exist before setting currently selected
page, which is still used in documents generated by the older version of
LibreOffice.

Change-Id: I6cec5fd3d2165f714fc01b596d3761890d87a4ff

Change-Id: I5021ef61d9238da352e13bdd81a2f3607d0fb4aa

Change-Id: Ifeecd82f98f9be9f90d293a7b68691f91d7bbc34

Change-Id: I3d3d7ca09d30f5d9358e48f5a2e030967aa16bc3

If the library does not work, things like fdo#67388 happen.

Change-Id: I3390fdb6f2cdf24145ddde4466146f91e5dfde82

Hopefully fixes fdo#67388. I can't reproduce here.

Change-Id: I5bcbb59a0f49e925d60f225b0f8f925d6d5dc468

start/end inside a table while end/start of the selection is outside the table

(cherry picked from commit 382814cc)

Conflicts:
	sw/source/core/crsr/swcrsr.cxx

Change-Id: Ibcbd9b18538ce04abfae11e75b30d6897a62e268

Change-Id: I0ed6f24d4aae0f62cb63c682322e39e635e49ec8

We should only enable bluetooth with explicit approval of the user, see:
http://developer.android.com/reference/android/bluetooth/BluetoothAdapter.html#enable%28%29

We now also display an appropriate message if bluetooth is disabled.

Change-Id: Ic3a07c9ad0806a60ac7c7e609a30add7af18916f

Change-Id: Iba539b5546b5bf0dca9c9f19f2537cbcdd48becd

Change-Id: I82bd41c42ade8da50741af4fa66992d4ea95c463

Change-Id: I23c20ebf77666a64e3b65ce69ada1c1e1cfa5c21

Change-Id: I2888be395e137ebc1f25cdc13626ec4265461523

Change-Id: I8a07b74c047dfa2c4b1096e3cd3ace3bd5f93d0a

Also, factor out common code from FlyFrameGraphic() and
WriteDMLDrawing() to lcl_startDMLAnchorInline() and
lcl_endDMLAnchorInline() to avoid code duplication.

Change-Id: Ic1bed48e45b1cdb2d061ed7099206c0b1aa4f9f7

Change text in status bar for moving average trendline:
no equation, no R²

Change-Id: I0e18a72ff1f1d78e3bb28cab4d5f215c096898dc
Reviewed-on: https://gerrit.libreoffice.org/7015Tested-by: Tomaž Vajngerl <quikee@gmail.com>
Reviewed-by: Tomaž Vajngerl <quikee@gmail.com>

This would test for white spaces in text import.

Change-Id: Ieefd4653c18dceb5e5300b8411207cca100e4653

...and while at it, improve generated documentation.

Change-Id: I6b80b19f18cd41cd01e272bbb6e91aad2f7853f3

The value written for an Impress time field is something like
text:time-value="0000-00-00T23:28:07" (in LO 3.5+) or
text:time-value="0-00-00T23:28:07" (in OOo 3.3) which contains an
invalid all-zero date.  Such values are actually rejected by the
ODF import since commit ae3e2f17.

Actually there was no real support to read the RelaxNG type
timeOrDateTime before.

So fix that by:
- adding convertTimeOrDateTime/parseTimeOrDateTime functions to
  sax::Converter
- recognizing and ignoring the 2 invalid all-zero values written by
  LO 3.5 and historic OOo respectively
- writing a bare "time" in text:time-value if the DateTime struct
  contains zero Date members
  (Older OOo versions and AOO cannot actually read that, but everything
  they _can_ read is invalid ODF...)

Change-Id: I754076caee74a5163ed3f972af0f23796aa14f9f

Apparenty an uninitialized SvxTimeField is created instead of the
SvxExtTimeField that is needed to preserve the value and format.

(regression from ee5fc5d2)

Change-Id: I36b16af0c143e8b5451a1925806756492dc2334e

... since 2f44516d

Change-Id: I25905a69464a43e12fcbb4770c8b0e171ab3271b

SfxDateTimeItem and SvxExtTimeField need to use 64-bit integer to store
Time as well.  These classes also have binary serialization
Load()/Save() methods but they are unlikely to be used in a persistent
way, just for the clipboard.

The problem is easy to reproduce in Impress: Insert->Field->Time(fixed)

(regression from 9830fd36)

Change-Id: I5946c5b94dd5a509805b6dc40461bbd910caffc4