Change-Id: I3f080f0c77ba7c5976c8b764e0c7e1f7c78ab47d

Change-Id: I14351561764811562a2c2904b6f7db6148e55c9b

Change-Id: I8c064788159b3cdd83f9ef0f4609e615db789cc3
Reviewed-on: https://gerrit.libreoffice.org/35147Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

...after 5ac443e1 "ToolBox::mbCustomizeMode is
always false"

Change-Id: I39bd9d07dfd8dee8e935aa612db35e11022f4ed3

and set size of buffer to successfully read data for short reads

Change-Id: I8d132446682104f2a4b8c476b7f2bda188bb3cdf

Place raw language tags in curly brackets {}, so all on-the-fly tags are
grouped together at the top of a listbox (but behind the "[None]"
entry).

Change-Id: I01d388150241a8482a1f39f8eda26cdd5bb1d832

... so they are available already at the first instanciation without having to
be added manually, depending on which listing is requested.

Change-Id: Idcb8f7fcbc82c757a2b06b8f04b81e88197a0a5b

never been used since commit
70de0c38
"MWS_SRX644: migrate branch mws_srx644 -> HEAD" in 2003.

Change-Id: I794aa890a222bcffb692db86772f8a1a5e76cb6c

Change-Id: I1354d4aa4d7e46cd3bf463e3350071aad3ff5674

This is similar to commit 92fd894e
(tdf#94435 RTF import: \ltrpar should not override \qc, 2015-10-05),
except that here the \qc is inherited from the style, it's not a direct
formatting. The problematic code was added in commit
2638faa2 (writerfilter08ooo330: applied
patch for writerfilter08, 2010-07-28), and it's not really clear to me
what is its purpose, given that the DOC import equivalent in
SwWW8ImplReader::Read_ParaBiDi() doesn't set the paragraph alignment.

Fix the situation by not touching the paragraph alignment for the RTF
case at least.

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

...after b2262e8b "callcatcher: remove some
unused methods" (and other clean-up of unused functionality that came before)
identified ToolBox::ImplStartCusomizeMode as unused.

Change-Id: Ic2c6720ca5519842796c7e993064aed637503aa2

Change-Id: I7fae0eb980b6dc655254da8b401fc1e71a4e65cf

Change-Id: I43ed9f53618dca09e0289bffadc2c05056e0eebb
Reviewed-on: https://gerrit.libreoffice.org/35149Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jan Holesovsky <kendy@collabora.com>

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

Change-Id: Ia6f2cc3a85f81c4853beea7a9f7b267a7fe89285

This is not needed; the problem was in the Fedora 25 epoxy headers:
They got badly broken in an update, and should not be used from C++
code. If you use Fedora 25, make sure to use --without-system-epoxy
for now. See https://bugzilla.redhat.com/show_bug.cgi?id=1431994

This reverts commit cbb2e6b7.

Change-Id: I55c77ff279f1716004ac77cd3a08c4bb3fdf644b

found with the attached bin/find-unused-rid.py script

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

For some reason this was not detected earlier, but now when the epoxy
headers in f25 were updated, it is.

Change-Id: I7be830153792414b0f913aaaecb2a1336ebf6fce

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

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

This test wasn't round-trippable because the page breaks were
all lost, and all of the frames ended up on page 1.

fixed in 5.3 daily debug bibisect 12a5c2be4d64199c6540969c645118112084a639
best guess: author Tamás Zolnai 2016-10-28 14:10:41 (GMT)
best guess: commit b927c1f4
tdf#103544: DOCX exp.: Image loss when have a frame anchored to the same para.

This doc still needs some work - the frames are shifted backwards one page,
so frame 1 is on page 2 and the last page contains two frames.

Change-Id: I512c1d66b742b29f1a9fe8644355f3d9df5ed1f1
Reviewed-on: https://gerrit.libreoffice.org/35127Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Justin Luth <justin_luth@sil.org>

Change-Id: Icf8a52db84536ef540c5dcffceabfbeb5c1deb02
Reviewed-on: https://gerrit.libreoffice.org/35153Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

Found by the "Random Condig" tb run #293.

Change-Id: I8fa7b66444b9b57f289c963cb1da5e772341dc30
Reviewed-on: https://gerrit.libreoffice.org/35156Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

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

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

found while changing base of SvxFrameDirectionItem to SfxEnumItem

> warning: comparison between ‘enum SvxFrameDirection’
> and ‘enum com::sun::star::text::WritingMode’ [-Wenum-compare]

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

Could have sworn I did this originally, somehow it got lost.
Also fix a thinko in tools::ResId I introduced in commit
2b70fb58
"Use o3tl::strong_int on RESOURCE_TYPE"

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

Change-Id: I5c7d1d47f347b3ce8de6e2e4995da8724a464941
Reviewed-on: https://gerrit.libreoffice.org/35045Reviewed-by: pranavk <pranavk@collabora.co.uk>
Tested-by: pranavk <pranavk@collabora.co.uk>

to skip a push to the stack immediately followed by a pop.

Change-Id: I97eb48db2521d640acec4d8080cceb56561eb901
Reviewed-on: https://gerrit.libreoffice.org/35129Reviewed-by: Takeshi Abe <tabe@fixedpoint.jp>
Tested-by: Takeshi Abe <tabe@fixedpoint.jp>

Change-Id: I38e622df87dd4b5e37dd248c5181978e13890fda
Reviewed-on: https://gerrit.libreoffice.org/35132Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

Change-Id: I6ec50033a452493852729dc8efe78da2708cbd96

Change-Id: Ibe41e1edb717b4e740971f4b972abdea769460eb

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

adds an extra SVSTREAM_WRITE_ERROR check to some of them, otherwise
they're all the same

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

Change-Id: I5f3e1a8fe559500aec7ea9e38edaba42dff3f98b
Reviewed-on: https://gerrit.libreoffice.org/35028Reviewed-by: Tor Lillqvist <tml@collabora.com>
Tested-by: Tor Lillqvist <tml@collabora.com>

Change-Id: Ia89f068d93b810b0c32df5df62a582322f3e5588
Reviewed-on: https://gerrit.libreoffice.org/35142Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>

No point in outputting the enum class name when we know it is a value
from that enum that we are outputting.

Fix some random whitespace craziness.

No point in putting that symbolic representation of an enumeration in
double-quotes. It is not a string in any sense.

We can pass an OUString directly in SAL_INFO.

Be consistent, put a double-quote on both sides of the string (font
family name), if at all.

This is a way too verbose commit message for such a trivial change.

Change-Id: I9e3f96856a634dc16f0e24f789c1898d7ec75fd9

Fix C4806: '&': unsafe operation: no value of type 'bool' promoted to
type 'int' can equal the given constant

Change-Id: Iedd54379a67373fb3499a0a780f2cbfc83f08e84

Change-Id: I376933a033a2dc2b5b7b59006b93d14a65463aed

Change-Id: I6b9423db247583ff1dcbd469db5dfab7f89e7457