Change-Id: Ifd20975b799ae63ff55a6b34f7d768831462648c
Reviewed-on: https://gerrit.libreoffice.org/55412Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>

Table line styles are now black and 0.05pt.

Change-Id: Ifa613c2c26ecb97e2d466e94a21c4120065969c9
Reviewed-on: https://gerrit.libreoffice.org/54461Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Muhammet Kara <muhammet.kara@pardus.org.tr>
Tested-by: Muhammet Kara <muhammet.kara@pardus.org.tr>

and fixup the "make unique if two things want to write to bitmap at same
time" check, it was using maBitmap before maBitmap has been assigned
to.
Lets just make it check something more useful, like the share count of
the underlying SalBitmap.

Change-Id: I97a629457174da2e4df1edc9674290aa9c9a2b52
Reviewed-on: https://gerrit.libreoffice.org/55416Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

Change-Id: I8f66b5afb066fe83abb83c56ebde6f21197f894b
Reviewed-on: https://gerrit.libreoffice.org/55333Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

In many cases you don't want to use a bunch of MessageBox() calls in a
VB6 client you are developing against LibreOffice, as that disrupts
the working of the client. The developer might not mind, but other
people trying it will be bothered by having to click through a stream
of message boxes. Also, it is hard to correctly interpret the
chronological sequence of LibreOffice's own debug output lines and
such MessageBox() windows.

WScript.Echo calls from a VBScript client are a bit better as they
don't require any click-through, but still there is the problem of
correlating with LibreOffice's own debug output.

Setting this StatusBar property causes LibreOffice to output a
SAL_INFO line with the tag "extensions.olebridge". Thus they are
automatically merged with LibreOffice's own output and displayed in
correct order.

Sure, the intent of some existing 3rd-party client that sets this
property would be to actually display a message in the status bar
(whatever that corresponds to in LibreOffice), but until some such
need is actually encountered, it's enough to just use it for this
debug output functionality. After all, this property was not
implemented at all earlier, so adding it now with somewhat special
semantics is not a regression.

(Note that on the Calc side, ooo.vba.excel.XApplication did have a
StatusBar property already, and setting that does seem to attempt to
display the text in some way. Possibly it should be enhanced to also
do the SAL_INFO thing, for consistency? And possibly we should also
have the message being displayed in the same fashion on the Writer
side?)

Change-Id: I5bf1e776d6401adfc43a558a2d919bd675298e1a
Reviewed-on: https://gerrit.libreoffice.org/55413Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Tor Lillqvist <tml@collabora.com>

so we don't need to cast at the call sites.

Also fix the type of mpExtInputRing in SwDoc

Change-Id: I60794a4b5c24ca552eafa87b8810dc08efdee3ea
Reviewed-on: https://gerrit.libreoffice.org/52455Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>

As the previous run of std::nth_element() already collects all of
smaller elements than the upper median into the first half of the
vector (which may also contain an equal one to the upper median,
that's OK), we can safely ignore the later half for finding the lower
median.

Change-Id: I64c97ee03b02ea363399077244dd99d0d10defcb
Reviewed-on: https://gerrit.libreoffice.org/55370Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Eike Rathke <erack@redhat.com>

We must compare the index against the number of entries with '>' and
not '>='.

Change-Id: I2de9e53b2a0d923d4136ee5e093baa955c8301da
Reviewed-on: https://gerrit.libreoffice.org/55405Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Tor Lillqvist <tml@collabora.com>

Project: help  4189aaf3b4d4c00773d5afb4c0ad5f0eea5820b5

Changing "Images..." to "Properties..."

in Help
as found by bubli
+ some additional cleanups and improvements as usual

Change-Id: Ife3f5ccd82ee1bf5329867820fa0b7da1b223444
Reviewed-on: https://gerrit.libreoffice.org/55153Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Katarina Behrens <Katarina.Behrens@cib.de>

Change-Id: Ic13bc488f2c8137eae3687d72732533ba5542998

They aren't needed when fpdfview.h is
included and clang reservedid plugin complains
of the double-underscores.

Also, wrap the PDFium importer class in
HAVE_FEATURE_PDFIUM to avoid build failure
when PDFium is missing.

Change-Id: Ibc285aea575acf72541866c534ef943e0bb89466

Change-Id: I58f2fd973a731b148f40b37139cd74bac097a7d2

Change-Id: I6c2c48c033facb317b4ca7ed2af07348d6386b98
Reviewed-on: https://gerrit.libreoffice.org/54921Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

Also allow for rendering PDFs to images at custom
resolution, instead of hard-coded (old hard-coded
value of 96 dpi is now default arguments).

Change-Id: Ia5b52f72d6ce7130a2debc7c6f86504aa041bdc8
Reviewed-on: https://gerrit.libreoffice.org/54786Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

i.e. no borders or larger page than rendered PDF

Change-Id: I1f356cceeec1d5d9f1728f0e29160fdd9241a221
Reviewed-on: https://gerrit.libreoffice.org/54764Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

Change-Id: I81225e228d9cf2b9849110715dbfdeb59f2805dd
Reviewed-on: https://gerrit.libreoffice.org/54746Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>

Change-Id: Ibb7734430b955dad4aefec22260ba8694ccb9183

Change-Id: Iaee679d2ff322c67d081185588103d5685fa970a

Change-Id: I79dde3c8983a70311de2d2a46093fac2722fb372

Change-Id: I07c6a7c65d5631b70da64927a35d7a3b371eff25

Change-Id: Id925ba7734a2c73270e40f19d3fc50552441c34e

Change-Id: I7675a183bfb691a8783950f33dc34826f91cb768

Change-Id: Ida5daa71d469805fd52e08e804fb9fa182d7d008

Change-Id: Ibcfd30383db6846e791aea7609ab196c4f3f2da4

Some PDFs don't include spaces in the text.
Instead, they rely on the explicit positioning
of each character to render visually separated words.
Latex seems to be prone to this approach, though not
exclusively.

Luckily, PDFium does process text and inserts
"generated" spaces where necessary, which is what
we retrieve and use as the text string while importing.

Change-Id: Ic21fe6c8416ecaba66f06b6260f1d6b040ff12af

Change-Id: I7d216ca61b8a10219628877db7dd593a4987ef60
(cherry picked from commit 81f16107)

Still missing the context matrix transformations.

Change-Id: Id9457c6475463127d3bc444f36fa373a6ec8fcb6
(cherry picked from commit 08e2c68e)

Change-Id: Ifa5f58163bef209a988fc0f88e2b609b1973e0d4

Change-Id: I5b25b3532912c7982a6db9dcc80fb7a72a41af38

Change-Id: I728d962ea65ad1671e3b4c76034d396bee84228e

Change-Id: I01cba9456b37bd7a63c823bbe332d686f7ede389
(cherry picked from commit 26e37f98)

Change-Id: I22880afdd9d36d9096003d86bba15098b465e0b3

Change-Id: I5b150721cc1b61b028f282062c1466ef6a67fcae
(cherry picked from commit 37a40d80)

Change-Id: I9a2fc2c8511655c1aa362c1a03a5e82ae3ba697e
(cherry picked from commit d057cf3d)

Change-Id: I8e63b2a35d841e065ef32fea95c0a5f22ca6f049
(cherry picked from commit 819d11b7)

Change-Id: Idba294cf5a3a8dd00988f94786715b110039e000
(cherry picked from commit b1083c11)

Change-Id: I7fa675c6560504e4fc7917e19cac3cceb2700d8e
(cherry picked from commit 3c02b52f)

Change-Id: Ia9f2fa1fbb24ad3466bd082b778244f451c90745

This makes it trivial to support all sort of
odd bit-format and 8-bit paletted images.

Change-Id: I4555794eccd0ee2906f9a39bd93957ad3775432c

Change-Id: Ibe8d794c1d457936c9272bb664a5478d78654dd4