Change-Id: Ia0dfe1e1ce1ab2b1ef266d1aa0950fd6670b0c50

Change-Id: I0d7c6f89f4646b59f23591eb1b3511afa31179c2

Change-Id: I5fce2b580dd2424f80c802c513ac229988212c58

Change-Id: I5071948d523bc8bd327cd66ee785e9bc2c173054

Change-Id: I526cb06b019b945931b24eb40477a1727c38cdc2

(...in the Windows-specific code path)

Change-Id: I5984ecd88a12d3f22aecaa685bd552f4235fb13d

Change-Id: Ice5d9d9e58886b752a7c88049a5f4e0986a7a86b

because we only get smooth scroll events, so implement that as
best we can.

Change-Id: I7701949cf7c9ffdc9d062f75b23db7c6add3c6a9

Change-Id: I59093e5d5eb1b3b1e14faaf32ac83b0ddb6b1d81

So no need to test after calling it.

Change-Id: I122bd5c2de23568b1cd3e98aef3c61d2ca91dfe9

Database._OutputToCalc uses LO filters to export table and/or query data

Change-Id: I69b15e76a490de32ec2cae73661f8ffd5f2b53b2

instead of just an initial size, because we can set a size-request for the
minimum size and that's a reliable thing

Change-Id: I83916715cb9e3dceb6e88f3ca8fc86920677c026

The function does not, in any way, as far as I see, make the
OpenGLSalBitmap object "current". It picks one OpenGLContext object
and makes that current. So, rename it to be less misleading. Am I
missing something?

Change-Id: Ia9f8e2415e1075dd5892cd40140e6ad764feeaa4

Change-Id: I0492c5b3018f59e4b783bb33f8b75ce67847dcf0

This only reads all the interesting info,
SwWW8ImplReader::Read_FactoidBook() still has to put it on the filter
stack in a later commit.

Change-Id: Ic2e8b441367448b5bdf940bf8871f25afe8362c4

Change-Id: I3889453be48aaffc8015fbbb5672d34e904c3770

Change-Id: I41b8514a127d463ac951e5855f09416fa0456b1b

Change-Id: I1df6ba8a269be3e165ff5948af1dd12e0bdc6f7d

Change-Id: Ia1af11514f6096ac55d561f729bbcba9ee5b0b14

...instead of being removed, a9824e8e
"cid#1326591, cid#1326590 useless call"

Change-Id: Ia71abff8fb821cb4904794e1f9cbeb320e17c629

Change-Id: Ie38ed19ea1637ae25846eef8a3e779d7b3bfe1df

Besides, the namespace was confusingly named the same as the public
cross-platform OpenGLWrapper struct (which is effectively just a
namespace, too).

Change-Id: I9a5255ec446dcdb5086d92a742f29327d0780685

This should fix a regression from 3bdd1767,
apparently the cppcheck's advice is misleading.

Change-Id: I427ecaa1eb3c9841cb6112997b9b51feda4583d0

Change-Id: I8ba75fcd2f98a49fe9d620af6b248f32911d7fe8

Change-Id: I11a8f9db15a576ff9926f8f827cbcc08a345ffa4

Change-Id: I43e52c2c982ed553a53be9839feff591c99fdfca

Leftover from commit 0ec0ec26 (i#93570
DOC import: handle commented text ranges via RES_FLTR_ANNOTATIONMARK,
2014-12-30).

Change-Id: Ifc2547ccb6bc91687ad61896b72367320210a837

to refelect various list of output formats in DoCmd.OutputTo() action

Change-Id: Ibb95020efa2995cde168efbd516f9b1e49d832a3

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

I was wrong for thinking that there was a problem when
elements inside def elements were not written.
Actually, Cristina's commit
( 5e27d23d ) was correct
as elements inside defs don't have to be written at least
they're refered by <use> element, which isn't supported in Libo
right now. Working on implementing support for use element

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

Change-Id: Idb0865f4d0db6c4eda33810ab2ef4cff49bc85d1

The idea is that a subset of the smart tags will be mapped to RDF
statements, as done already in the DOCX importer.

Change-Id: I46e0dad37a3905fe591cba0f710156f27be05ff4

So that later SwWW8ImplReader can read these smart tag position
structures in a way similar to bookmarks.

Change-Id: I0e1dc30d48bbb6641a82d777f6569f59dd922e16

This is similar to RES_FLTR_ANNOTATIONMARK, except that it'll be used
for WW8 import's smart tag bookmark needs.

First just add code so that WW8 import can put this this attribute on
the import stack, the actual handling of the attribute has to be
implemented later.

Change-Id: I92e3fac02496e3f5e7a6ea27f0da91dcd47769cc

...they don't cause any change in behavior, likely they predated Noel's figuring
out the template part of containsWindowSubclass

Change-Id: I0d5b6bd7f228acef9a0ce1c85fe98fbab89bd7a8

This enables rotatad/flipped icons in the Sidebar and other non-toolbar places (tdf#85767)

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

Experimenting with different non-alpha characters in front of
field, most of them aren't allowed and result in field not
recognized by MS Word: #$%&'()*+,-./:;<>?@[]^_`{|}~
Besides, if backslash "\" is followed by another backslash or
space, it is illegal, too. This patch takes care of it.

On the other side, not closing quotes is allowed by MS Word.
This patch allows this, too.

The patch does not handle another allowed field code "=2+2".
This should be done in another commit.

Change-Id: I842fe59c026b68977e61a7ae0b5495c02803ad83
Reviewed-on: https://gerrit.libreoffice.org/20435Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>

Write a \par at the end of each paragraph instead of writing one at the
end of the whole text only.

Change-Id: I984b31d4ae3d2e728c993b25bfde761dcad063ae

Change-Id: I8a1678d1677dbff82b6785834e63007c2c3e9924

is removed here: 449d272d

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