Change-Id: I9508a947e5ae6720516d9f926a59d4287cb15317
Reviewed-on: https://gerrit.libreoffice.org/20166Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Tested-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>

* Remove unused fields/methods/includes
* Formatting

Change-Id: Ia4a2fba258ddf00e8fe507338f7f8c7388631f0b
Reviewed-on: https://gerrit.libreoffice.org/20164Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Tested-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>

Change-Id: Ibc95574848752111d36cc9b3ff13709921b67e6c

Change-Id: I2d1185d433be0fbb57a59e0609ab0f505248a348
Reviewed-on: https://gerrit.libreoffice.org/19210Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Tested-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>

comparison is always true due to limited range of data type

Change-Id: If4bcf1f3123cbbd9261e48d2c786a610fc7c0cbc

Change-Id: I59d9f7f73677358b4ae57efda965d43718bdf0d5

Change-Id: I979743671e9a2e868d815f917427588b7b0320ba

and fixed bug in sepia filter, where it was using the
wrong member of the union to get the percentage

Change-Id: I56b76496a3ac711adec12dd8c08b28d69644d66f

The old code in MultiSalLayout::GetTextBreak() only makes sense if the
base level character width is zero where a fallback level has a
non-zero character width, and vice versa. But this is not the case for
Windows, at least not any more now when using UniscribeLayout and not
SimpleWinLayout.

This simple change fixes that: Only use the width from a fallback
level if the width at the base level is zero. Hopefully it does not
cause regressions for other documents or on other platforms. (But, I
repeat, I find it hard to believe that the intent of the code could
really have been to ever add two or more non-zero widths for the same
character from different levels of fallback and use that.)

Change-Id: Ic66c55db4b7463f9e04fcedec76f1c44f5e62e03

This commit renames the most annoying abbreviations in Writer (and
partially in the shared code too).

Change-Id: I77e5134f42f25e3786afa36b7a505c7e3237a9e8

some of the fields

regression from

commit dd351dd7
Author: Noel Grandin <noel@peralex.com>
Date:   Tue Nov 24 08:50:39 2015 +0200

    loplugin:unusedfields in vcl/

Change-Id: If68bf1e0ce90ee3c513f5461d5acd7a32e238d7b

Change-Id: I5975af2801560c61ca72ab25f5d1222cf847c4e3

Change-Id: I1581b28237d2b9f9c22d3f3b0436dc281508aafa
Reviewed-on: https://gerrit.libreoffice.org/20118Reviewed-by: Katarina Behrens <Katarina.Behrens@cib.de>
Tested-by: Katarina Behrens <Katarina.Behrens@cib.de>

Change-Id: Id960540977eb7d0d5f3bdc1c5737137a0d3694b8
Reviewed-on: https://gerrit.libreoffice.org/20117Reviewed-by: Katarina Behrens <Katarina.Behrens@cib.de>
Tested-by: Katarina Behrens <Katarina.Behrens@cib.de>

Change-Id: I1c58da68525ccfe8726a07e40dd8c7db89616580

Change-Id: I82678b037aff5409e54bc50744b1b4b2c8d4d83b

Project: translations  9b7a6f9619c88ddee34c8cd1623eccdd7d4a4769

Update translations for master and force-fix errors using pocheck

Change-Id: Ia185c1d9ef3b66189ec6b1ab08795fa5f4aaca49

Change-Id: I22966b66b1b8e4dff2e565de456f21a668f33f28

Change-Id: I946c64d103f3666e5bbff16d95a5c8e65a3750dc

Change-Id: Ia2dd13c2c48b127ab85311a668fa1f37608d360a

Change-Id: I3eb27ed10e82ee56b33866ac576c1b1f8c9756b9

Change-Id: Iadba30885ba3bab7aaee58e298a9dc6b22c8b977

Change-Id: Iaa57a071f8f0e6945d24f019cb4c06e02d066e0a
Reviewed-on: https://gerrit.libreoffice.org/20147Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: I3b1f51d3a02b999476d12e680f2f76a11ac6b3b9
Reviewed-on: https://gerrit.libreoffice.org/20146Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: Ic5d1090722945dce338973e9e3091546ed792057
Reviewed-on: https://gerrit.libreoffice.org/20160Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mikekaganski@hotmail.com>

This reverts commit 22ebafe8.

It seems to break various sc.subsequentcheck targets.

Unknown names make the formula fail
PythonTest_sw_python, especially set_expression is ok
Variables are taken into account

Thanks to Mike Kaganski for his help on this patch.

Change-Id: Ia6f9c54d90ce88138fd9c9df9422b34ce8223ca2
Reviewed-on: https://gerrit.libreoffice.org/20122Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mikekaganski@hotmail.com>

Change-Id: Ib53eb3da4810202ad60349566cdef74be89418c8

Change-Id: I58d9d7dcbcd1e6cf5ae51532982d7d3525038984

The idea here is that we should process 'idle' events - like re-paint
after we have processed any OS messages - such as key/mouse input,
window re-size events etc.

The previous approach wasn't achieving this - it was processing a single
idle event each time around the main-loop iteration; urk.

Lubos implemented something -like- this, the vestiges of it need cleaning
up and removing in: 06d73142 but it was
disabled (most likely because it broke gtk in tdf#91727, which was itself
broken by using silly values for timeouts in the scheduler (now fixed))

Tested on Windows, gtk, kde4, unx-generic.

Change-Id: I7756bca874779c00f72b372cacb7745d0f189f66
Reviewed-on: https://gerrit.libreoffice.org/20158Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>

we were reusing the stride of the surface we were cloning,
but the new surface has a different underlying size.

remove the custom stride argument and just change our stride
calculation to use the same scheme that cairo and GDI uses, which
remove another platform/drawing-system variable

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

Change-Id: I52854241a9ab87153635b27cb6a66ef4269b2e76

Change-Id: I9a0d92dee7cebecfb7b204628738f716b901771a

Change-Id: I546ae14d49bb64fb069a4a5d7dc7685e823ea3c3

Change-Id: Id05a77b83783c0e12a77bd5e91e595fa0ae29629

Change-Id: I1d3ad22b3dd304ff7384de1e07af88cd63bd28cd

This fixes a bug with glib, where prepare of a source with such a
large (max uint64) causes precision & wrap-around problems.
Add assert to avoid recurrence.
Also add a helpful user-visible source name in debug mode.

Change-Id: I9e1eb41af9cc49f8bff88e07f04d4bc4d1877376
Reviewed-on: https://gerrit.libreoffice.org/20152Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>

And add only the minimum amount of operations we are sure about.

Change-Id: I0dd35968206161e31fcd8bfd0b647329c703e0da

This is a ScMatrix implementation that operates directly on
formula::DoubleVectorRefToken, saving tremendous amount of copying data back
and forth.

Change-Id: I027e6cb668ef40eb474773a0ce8d0eeefc1ab71c

We want to introduce another type of ScMatrix that will directly contain
DoubleVectorRefToken and operate on that.  The idea is that it is pointless to
construct a ScMatrix via lots of copying around, when we already have a nice
array of doubles.

Change-Id: I3e5d7b9e2e0f9b9bf350336a8582cfd852586b3f