49c2b980 changed a binary test doc

Change-Id: I77cd86ce3eccfc701f54630870045e04244ac048

Change-Id: Id1b1de27752a6b8a74ea3521b53c38f032bfa24b

Change-Id: I02763bc1dfeec4a04f40fa0246cdc93eab6d6d33

Change-Id: I90e1e147357d6509024f807bc2f777141e79b586

quartz doesn't impl them either, so presumably its not too bad to
not have them. Can't see anything visually ugly at the moment
to warrant the effort.

Change-Id: Ibf6119f549ab6712d3f1aca18e2cdab905f00030

Change-Id: I6dde11f291b09db82f14674d69b84093989eed28

Change-Id: I206701fa068c788f77307a649a607316473e6105

Change-Id: I5babf6365c50b7c5ad58cdb74729b9a8ac1c4ebc

Change-Id: I654fc22bbab2301e74cf200577f934e56f77fb58

ah!, the original code had a type in it. That's
why it was refactored to remove the null check.

Now a proper fix for cids: 1326180<->1326190

Change-Id: Iba7fd47c03eb5c157f878e0e297e8688f20ae348

This is (worrying) fall-out from

commit 229fc164
Author: Philippe Jung <phil.jung@free.fr>
Date:   Fri Jul 10 17:02:44 2015 +0200

    Impress: Rework the way the display modes are presented.

Change-Id: I00d19b2d3cec4d505d17ba4031f6763c86395f74

Change-Id: I30ea6cea81ae1b4f344e253c7a51cfef4d844128

Change-Id: Ibd1c15ce65501d4dc6d0cea8c8e5f4e683d1b7a4

Change-Id: I9f76340ccdb32f4337d0ebe85e9957fe8a3b19f9

Change-Id: Id984cc1f5954be38fbe3a1a15bfe811d7cdfe99d

mostly anyway

Change-Id: I21d7f46ba018c3ed81093873da35b883efa44d66

Change-Id: I2ac61cd2a99da25122165af692154fdbc2ac6d2e

by stealing the quartz impl

Change-Id: I548042328144e23c68b83e461a63cdb0d7d8ff2c

Change-Id: Iff2a651384cc96f541dba2f9e134c7463619c62c

Change-Id: I1c46f38927c48070e5739b99de96d61943837a14

Change-Id: Id1615ac223cd6257a419e8abe39b5121d4c16ca4

"errorOccured" is an English spelling mistake, but is the
name of the event, which cannot / should not be changed for
backwards compatibility reasons.

Spelling was boguously "corrected" in:

  commit 60a9b517
  Author: Takeshi Abe <tabe@fixedpoint.jp>
  Date:   Sat Dec 4 12:56:38 2010 +0900

      Replace all occured, occurance etc.

This was leading to impossibility of assigning a macro
to that event, since it was not appearing in this dialog.

Change-Id: Ib0373501cba8af8f4abb1c62faddf8d65c926a7e

"(abc)|(def)" matches "def" with result offset sequences
{0,-1,0},{3,-1,3}

And thus the assert() calls introduced with
4cf1d290 and
ce91f3c1 were hit.

Change-Id: I571b6c7d47349a2cc7b1d1e34193b2865012a49f

Change-Id: I97339c43605a838a8fc329b4f1daa05f584ee864

Change-Id: I1fb5baabd869c4abe8ccf9eeae131efcc697bbee

Change-Id: I8c8cd6255b6722d4d46d6e652e9d9d9722fe112e

Change-Id: I835f8e33565d20d9fe371cafeededdd32f157f98

Otherwise we get workbook load events (eg.) happening at idle, which
occurs at (more or less) random places as the StarBasic interpreter
Yields every few instructions executed.

Change-Id: I51ea57f4ad45e30e04fe84a9dc051ed1c5537536

Change-Id: Iee56131a15f9554c263406356456f65694515719

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