Change-Id: I516ca96c0743840fb03d8208f7236ca25027bc45
Reviewed-on: https://gerrit.libreoffice.org/20102Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Change-Id: I8f9e74f7fbbff055c67cafba5d534db4635e5399

TODO:

- Clean the now unused defines/resources.
- Several submenus are duplicated (in the menubar too). Makes
  sense to refactor them to separate popup menu controllers.

Change-Id: I85505eda1c5fb707b1e6064007f27af7b31452bf
Reviewed-on: https://gerrit.libreoffice.org/20704Reviewed-by: Maxim Monastirsky <momonasmon@gmail.com>
Tested-by: Maxim Monastirsky <momonasmon@gmail.com>

("'<<' : result of 32-bit shift implicitly converted to 64 bits")

Change-Id: I738fe94ec559e2a35ffc32fb91c22c06094cff9f

Change-Id: I326d306af89dcb0611e07689d2c26a828f3896ee

No testcase as our importer doesn't read this structure, but Word
complained about this.

Change-Id: I91f947233802ea6fb103c32fd774bad09c56764e

And also relax two import conditions, as it turns out Word accept those.
So instead of checking for each offset/length one by one, only check
once.

It's now as good as the DOCX one, I believe.

Change-Id: I1890ef61fdbbd2ab6facaf3e787f75b791adcfdc

have buuild under windows with debug-util

Change-Id: I65f5c52db0d57453bbbba268ba0b936588c2bf73
Reviewed-on: https://gerrit.libreoffice.org/20657Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>

side step the whole pile of misery by using native gtk tooltips

also gets transparency and native themeing too by default

Change-Id: I59552661cd9dc18a563341885bc40fcdadc5264f

this will make it easier to implement native help tips

Change-Id: I984dfadaf02e9b7bf542ba82cf070911c89cb699

Change-Id: Icef8c521d6a0ad1ee1fa1eadf2e472910c9193f2

Change-Id: I1d1f8aa28438209fbe3258b4b4418fcdfaabf78c

Change-Id: I05eda6067308119a388238eed356531851000691

Change-Id: I30ba25e035fae08c06b17e2bafcb8a1147d4e12d

Change-Id: I3ca21608d633145c8a5238b947e22671460e9195

which makes modal dialogs (which are most of them) place correctly
under wayland. Modeless ones are still uselessly shoved far to the
left, but this makes things near usable and gives the same "graying
into the bg" effect for the main window as other gtk apps

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

Throws exception to manage timeout early in the first connection
sequence.

Change-Id: Ibf87f9d7607c808692509c694127266b6f542014
Reviewed-on: https://gerrit.libreoffice.org/20196Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>

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

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

It keeps state that apparently doesn't affect its cache hash key.

Change-Id: I82ead9fcded16152f2a106a971484cf4a9eaf8ea

assigning a component or a script to a dialog control should not results in a crash in
dbgutil-enabled build

Change-Id: I06d11d8d51d0fe8d1b2a7217c51c1dfc8d3f8c97
Reviewed-on: https://gerrit.libreoffice.org/20695Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Oliver Specht <oliver.specht@cib.de>

Change-Id: I0caab9e329a465e10bf3ed321c55c287371bd437

since

commit 7650a60b
Author: Stephan Wunderlich <sw@openoffice.org>
Date:   Mon Feb 3 15:42:43 2003 +0000

    CHG: removed obsolete lines

Change-Id: Ic03a2619a974005bbd2a60326a3dddb8cc394f83

Change-Id: Ie840cc41ed2c57da3793bdf370ed828242febceb

Change-Id: I70e241933b899b00bc4a3a959c900f284e6ec1ac

Change-Id: Iea1398d6c261659843d060fb0128f7a404beafb7

Change-Id: Ieef22ee987d486a8d7f994900a1f5fd61b0d8cce

since

commit 6eda3212
Author: Vladimir Glazounov <vg@openoffice.org>
Date:   Tue Nov 21 13:12:59 2006 +0000

    INTEGRATION: CWS qadev27 (1.5.20); FILE MERGED
    2006/06/26 07:05:08 cn 1.5.20.1: #i66737# enhancements on property 'NumberingRuels'. Now the test checks also of correct XIndexReplace values

Change-Id: I7e4a59e9b6d7cce044269af37f47fe75b65c56f7

This contains the name of the bookmarks, except that factoid bookmarks
don't really have names...

Change-Id: I0fe3b983edf206d51e4d1cf4a66919fce0167738

Change-Id: Ibefc4b908c752a6256b168b4045afb400ba8b17a

... to prevent duplicating masters on slide copy-paste.
Also fixed a 10-year copy-paste error (pRefPage wasn't replaced
with pNPage).
Fixed argument evaluation order issue (aStream.GetEndOfData()
depends on Flush() but doesn't call it, so will return incorrect
result if called before aStream.GetBuffer()).
Replaced compare of hashes with results of stringify(),
because it removes useless overhead (hashes are calculated from
stringify() anyway, and are not cached anywhere).
Removed Flush() called from SvMemoryStream::GetBuffer(), because
it calls GetData(), which calls Flush() itself.

Thanks to Andras Timar for unit test framework.

Change-Id: Ia46d4e9a017fc628d424949a9d229045a249a4ca
Reviewed-on: https://gerrit.libreoffice.org/20367Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

It referred to the previouly removed
Primitive2DContainerToPrimitive2DSequence(), not to maybeInvert().

Change-Id: I77dad2218d5b3e2e2d76673bd2e97d856d0b94f2

Change-Id: I9048966bd41e79bb7a2e9bd24c1dc611acefef1f

minor update to clarify unstable features against macro (limited) features

Change-Id: I30c782144e5dff3c300cfcf431c745597f0c3db2
Reviewed-on: https://gerrit.libreoffice.org/20688Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>

An .odt table can “keep with next paragraph”.  This means that the entire
table may shift to the next page and all the rows will keep together as
the table attempts to stay on the same page as the following paragraph.
There is no “keep with next” property for .doc tables, but each row CAN
be kept with the following one.  When exporting an .odt file to .doc,
setting each row like this will keep the text flow similar to the
original .odt's layout.

This commit only hinders the table from splitting - it does not actually
affect keeping with the following paragraph.

This functionality already exists in the code, but was broken
by a variable that “changed meaning” almost as soon as the
functionality was introduced.

A followup commit will deal with "full page" situations when the kept
sections are too large to fit on a single page and so the table should
split instead of start a new page. The only situation that can't be
handled nicely is a single table kept-with-next that spans more than
one page. Such tables ought not be marked as keep-with-next anyway.

Change-Id: I401772b3fa2e329b7b0890e67639cbca8c845206
Reviewed-on: https://gerrit.libreoffice.org/20217Reviewed-by: Justin Luth <justin_luth@sil.org>
Tested-by: Justin Luth <justin_luth@sil.org>

Change-Id: Iff1a0eb8e4b112b874813023551a797320ac0ad5

Change-Id: If490e8523dbedabdf4124b1bd1a5ba08678dc06e

Change-Id: If05602bf0fbbae0a669913e56add92ed902141c0

Taking into consideration the changes from
https://gerrit.libreoffice.org/20446

Change-Id: If2419574611b890170e9d5eb69703e5c8c21c3c2

32nd and final distinct crash fix of this sequence

Change-Id: Ib9f41091737e66995f332c06083d51408eb1497b