LOK is Linux-only at the moment, don't bother with disabling each and
every unit test on Mac/Windows for now.

Change-Id: I2ff1ed47251c16ec6a8d43138789480d95ea720e

Change-Id: Ia566e983548a89d974c133823da2f07d5c2e35e4

Change-Id: Ib989a23e5ece49b6eb16b25bb1fb6f635df25829

As long as we don't tweak the map mode of the comment widgets
permanently we also have to disable the selection engine's timer, as
that would emit events without the correct map mode: so disable that for
the LOK case for now.

Change-Id: If377ff2f064c30feb473f153f9d5b29b8ace7113

seeing as its unavailable for android at the moment

Change-Id: Idc4dfd01224a2b90eacce0efd2d1b8a75001d085

Change-Id: Ic2cc5aa50be39c1337c9831303ae2e5238573ddc

Change-Id: I72d9b1a2729d455431583177208597c554945629

Change-Id: Id63bbdd11af66de6be8a3e9dfca1c7efbe74b08a

Change-Id: I1d8b40843de8d9bb9e4113442bc083c21a7b278d

With this, pressing ctrl-alt-c to create a new comment has the correct
cursor position.

Change-Id: Icb8d708dab015d8ffa9bcfe28de66238a75b50bc

SwPostItMgr::registerLibreOfficeKitCallback() already took care of
informing existing outliners, this commit gives a callback to newly
registered ones as well.

Change-Id: I660dcb54231a9d404bf80b4284003d119dae6a5c

So that it's possible to drag the text selection start/end handles in
comment text when there is an existing selection.

Change-Id: I3acc4770928d4f385f0ca09a2484a9e112409907

With this, newly typed characters show up instantly in comments, not
only after changing the zoom level.

Change-Id: I1470db1ec03cc415917375f1f95434cf0944e559

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

Reviewed on:
	https://gerrit.libreoffice.org/19962

Change-Id: Ic91ebf4a18a77704dc1ccd1e1180b42d0bc84c74

Change-Id: If6ced6d33dbb9c82c75aa05a9f7b018926c0ffb0

Change-Id: I3e6e18a0bc224ba6d201b476d77e82571ef2ee69

Change-Id: I785b50d6f09db79d3184a19c01e71ef26c11b1d1

Change-Id: I9a31850ac3524b8f2fae6513f4d378f8616eb30d

Change-Id: If7607c45c7645a6b32ea3cad0f9f7eca6635ace2

Change-Id: I3a49fd336961b860f4b19b37a8d18cef8e4a5557

Project: help  9b62f36c82b8f7b15a8ed5ec062d73bef9a820cc

remove lastedited element from dtd and wiki converter

Change-Id: I4eeee9b3a00a197ec915c9996ace0249546f2319

Change-Id: I135c14c90d791959f36dde5dc50687cc09f2a151

Change-Id: I32bf78bcb44465bbe4c62e7ca144e801770ec53f

(cherry picked from commit 902cd9fe)

Change-Id: I7cac635d9e7b6eae93466ced0349edc01caab0c2

This looks like dead code anyway? Evidently it didnt' compile like that.

Change-Id: Id6500c18d66c6932b24c15b653d992c449e260c4

Change-Id: I59831588fb7bc7e907fbffb24ddfe068552b6492

Change-Id: I8b0475a6dcde53202a489b9d3265add9fe068cbc

Change-Id: I0ec07eb25d538d82d740a33f05b0a4f002adf36a

Change-Id: I2dfc80c05a982038bf374eae975fac8294bf4dc8
Reviewed-on: https://gerrit.libreoffice.org/19879Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Jenkins <ci@libreoffice.org>

Change-Id: Iee60389ccc9e348db6ed00e48e32b1e86f17b530

Change-Id: I1f7fd98b243c49bfd90060b297bb2391cb102bb3

After many years of careful investigation, we finally managed to solve
the mystery: it turns out that Windows has different line endings than
UNIX, which results in different hash values starting at m_nLinebreakHash.

Change-Id: Ib5fab7cd43ad10ea9a33c29857c5b53c84e623fb

LOK always works in absolute twips (origo being the top left corner of
SwEditWin), so not only the callbacks have to translate relative twips
to absolute ones, but the opposite have to be done for mouse event
coordinates.

With this, clicking at a random position inside a comment places the
blinking cursor at a reasonable position, not always at 0,0.

Change-Id: Ic8d20f177acd9e1908acf17698c53a1470bd4aec

Change-Id: Ic052544b2835181652732b8de9eaf79572a9db6e

With this, selections of Writer comment text show up at the correct
position, not at the top left corner of the window.

Change-Id: If865503d9a02a27730e382d65c42c706dd533a93

Project: help  7e12b71f3d846b392053bc0461767272e73c9e69

assorted typos reported via pootle

* 113,3 → 113.3 (en_US uses dot as decimal separator)
* typo: equivavlent → equivalent
* typo: "The the …" →  "The …"
* typo: "The Expert Configuration dialog let you": let → lets
* typo: "one of the displayed theme" → "one of the displayed themes"
* typo: Sidear → Sidebar
* spurious tag "<emph>.</emph>" →  "." – dot is just punctuation here

Change-Id: Iad058d285f2cdca6e32bc67281d3a4e9e1c18b65

Change-Id: I8df003bdad4430a174815ce51197b997717ef379

Prereq. to enable runtime SSE2 detection is that the compiler
supports it in the first place. MSVS and GCC use different
compiler flags for this so use __LO_SSE2_AVAILABLE__ to make this
build platform independent.

emmintrin.h is unavailable on ARM Android so include this and
compile the SSE2 specific code only when we are sure we can build
SSE2 code (__LO_SSE2_AVAILABLE__ is defined).

Change-Id: I212c4e0b99a314d087b9def822a81325b25f3469

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

implementation can indeed be empty when cppu::writeSharedLibComponentInfo calls
getEnvironmentFromModule(mod, curEnv, "", ""), which in the final if-branch
calls getEnvironment with implementation = "".  Happens when adding desktop/qa's
test-active.oxt.  Regression introduced with
ae3a0c8d "Add .component <implementation
constructor='...' feature."

Change-Id: Ia70958e4aa18d378ff35063bdf6187f6e073b765