The WriterSpecificAutoFormatBlock class actually writes a length
into the file that covers the offending SwFormatVertOrient item.

Put in a gross hack to read either 32-bit or 64-bit in
SwFormatVertOrient::Store depending on that length.

The length also covers another item, so we'll just hope nobody ever
changes this stuff ever again!

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

Change-Id: If63f004c95208d49743f389746ca430ad91e1231

There exists no documents produced by LibreOffice, where text on OLE
objects has worked, because import expects the paragraphs inside the
draw:object element, but LO has written them outside. The patch
changes LO to write the paragraphs inside the draw:object element.
The patch does not enable LibreOffice to read the paragraphs in
old documents. But versions at least since 5.1 will be able to read
text on OLE objects from documents which were produced by versions
with applied patch.

Change-Id: I879135f1a869e46c32361db653ede05227bab95e
Reviewed-on: https://gerrit.libreoffice.org/43696Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Armin Le Grand <Armin.Le.Grand@cib.de>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

Change-Id: Iec921c19336fc87b2fcd4bfe18676ff13b109889
Reviewed-on: https://gerrit.libreoffice.org/44364Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: andreas_kainz <kainz.a@gmail.com>

... instead of an arbitrary reference range read from a binary
file format, here 4k sheets resulting in >3GB allocated listener
memory.

Change-Id: I629297f4249fdf16a0ede098b63d9648fda69ac3

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

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

Test: English word "Ian" are "item" are not allowed as "İan", "İtem" now.

Patch list with commit ids in Hunspell repository:

commit 66badb7449c2053c89456f11a7f71f3f5916b550
Extend dotless i and dotted I rules to Crimean Tatar language

commit 88cf975c295e3ec808efb77bb1a2a031d77f0c89
Allow dotted I in dictionary, and disable bad capitalization

commit 39b785a6b03b35cc8a27f43f6005dcaa432694e1
FORBIDDENWORD precedes BREAK

commit 0f691abe68788d0a58e72ab66877a9f670cd2741
Remove forbidden words from dash suggestion list

commit 15b2cde4f01706f0a648518a5cfc57394d015448
tdf#95024 fix compound handling for new Hungarian orthography

commit de3ae6844af62300e473f7b7b66a56e54153b4b9
fix compound word part "pa:"

Change-Id: Id12b5629b0c975464072b5b144743cbe40fe45a3
Reviewed-on: https://gerrit.libreoffice.org/44200Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Andras Timar <andras.timar@collabora.com>

No idea how to check what fonts are installed on Windows/Mac;
only safe thing to do is to disable the tests if --without-fonts.

Change-Id: Ia27d866d9964f7e4e1ebfaba7ee4a7ce53b800b0

The TEST_FONTS_MISSING is already handling the --without-fonts case,
but if we build fonts we need a dependency.

Change-Id: I5164fc5c5974bbce7481b0b1ef4d6013eb9c0a11

Change-Id: I286c685aad38b850c3b988b7f9ba418092746d66
Reviewed-on: https://gerrit.libreoffice.org/44257Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Ashod Nakashian <ashnakash@gmail.com>

When including a PDF as an image, it's represented internally as
a Bitmap with additional PDF data. On SwapIn, LibreOffice just
imported the PDF data missing the PDF preview. The Graphic also
gad the wrong image type, which results in a busy loop on master,
with a strange / unhelpful STR_COMCORE_READERROR generated by
SwNoTextFrame::PaintPicture.

This is a workaround to generate the Bitmap on SwapIn, which
will really slow down LibreOffice when importing many PDFs.

I guess the job of generating the PDF previews should probably
be deferred to a thread or a low priority Scheduler task, just
like the general image loading is handled.

Change-Id: I8084e4533995ecddc5b03ef19cb0c6a2dbf60ebd
Reviewed-on: https://gerrit.libreoffice.org/43906Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>

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

Project: translations  b990191434c16fd9253cfda7854589f41728d836

Updated Slovenian translation

Change-Id: I80f31efc782ed5a46490e70bdc4916b5a2fe8b7f

As in https://gerrit.libreoffice.org/43987

This is for string literals only. Variables and functions like "nKorrValDecl"
and "GetRmz" will be translated on a separate, later Gerrit change.

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

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

Change-Id: I3f84396def32c657f58842647e9af5d4a48e43be

1. Linking problem on Windows due to Windows macros via
   <vcl/sysdata.hxx> include
2. Drop the custom MOC target for the old KF5 plugin
3. Correctly handle QT5 build without using QFont
4. ImplJobSetup is in the VL library, not the gen plugin

Change-Id: Iad97b1b9b57a8c356aaa88178aff03d0c14558c7

Change-Id: Ifea73d81ba3863fd6a99453cb38303eb729f6ff4

Since we implement SalGraphics handling like the gtk3 backend, we
need damage tracking to queue updates.

Since there is no native damage tracking in Qt5, we have to log
the damage in our subclassed QPainter, which will queue an update
on destruction.

Change-Id: Ife17770750a5be9959c2fc2633b422908d196869

Change-Id: Ide2ef42110798ed061f7e32e49e38b6428c22c01

Change-Id: I53807bff3db9c9e4300f03e56857381cad7c9431

Change-Id: I85ce73e0e79927fa9233230bc4a9134db4c513dc

Change-Id: Ie8684cd4be56fb6d88d9643a6326307590115a80

Scrollwheel handling seems to work with mouse, but not correct
when using a touchpad - at least for me.

Change-Id: I4f1b32205516912e31f9c52605ba2bf4ec6059a8

Change-Id: I36631c332ddffbca73768cdc4a596213e0b026ef

QImage stores the scanlines from top => bottom.

Change-Id: I0a176066ab631179b8460b61a6c2b07ad2179d31

Change-Id: Ie47b8def36d67255b61eab04bc7e3818bb1d8ea8

CommonSalLayout doesn't rally have an interface. It's cluttered
with #ifdefs. Currently we have to move the Qt5Font into the
VCL library. Someone should refactor this...

Doen't render any text yet, but reports some sizes.

Eventually that would cut down the public interface again.

Change-Id: I12f32affb05b37e070c6cbc80db01779f84590b6

Instead of QImage, this uses cairo_surface_t internally and just
blits the composed image in the Qt5Widgets paint function.

To enable this rendering path set SAL_VCL_QT5_USE_CAIRO.

Change-Id: Ieddda9bad2596ce46d7d07d4d7060e40d44997db

Move out of unx, as this will eventually compile on other
OS platforms. At least currently it doesn't contain platform
dependant code.

Change-Id: Iea0bebf574201881ea158381fe7ba8af2a9a6488

Change-Id: Icc322ea94708f0799011a2e4ee1499c184254690

Change-Id: I1f7b1894272096a0f0b23b63c3eeae310fb28c6f

Change-Id: Id8d901e9d283ee93cc952e6af267dbafd7f9b9aa

To pass the "Application error: no fonts and no vcl resource found
on your system" failure from OutputDevice::ImplInitFontList.

Just saw there is a SAL_NO_FONT_LOOKUP, which probably also would
have helped.

Change-Id: I2c818313c4f8b0f1d36242281e5c51973315b642

This way we pass the "No mpGraphics set" message.

Change-Id: I097a823c295b251304dfbec8a71eba31b3d2b9ef

Change-Id: I53845519d0dda324c9544f057b18c6afd4cf858a

This turned out more tricky then expected. Originally the
KAboutData was assigned to a non-existing QApplication object.
Somehow this was prevending the later crashes, if the QApplication
was initialized before KAboutData and we were creating QWidgets.

The problem turned out to be the referenced arguments to
QApplication. While we already passed the command arguments from
allocated / heap memory, the argc argument was just the local
stack variable!
The simple fix is to allocate an int to pass to QApplication and
the crashes are gone when assigning KAboutData after QApplication.
Also removes some Qt initialization warnings on startup.

Change-Id: Ic5b1eea578039fd5875097d23de587b970a6dfca

Splits the configure checks into a Qt5 and KF5 specific part.

Change-Id: I0a616ba031e1f7fd0385219ac48179adb4bdaf14

Change-Id: Ida7c4858cb770d1ce2d05aa6adc332c89bddd795