fdo#74302: Adapt to OUString changes and set length exactly.

This was fixed in master by 4c539fac018dfd44cd8db52161a8cb930c627da7

Change-Id: I69219e643f5eff3126191220ce2b1d0e1089a93e
Reviewed-on: https://gerrit.libreoffice.org/8808
Tested-by: Michael Stahl <mstahl@redhat.com>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
fdo#63786 rhbz#1081968: fix PDF export of cropped SVG

When a META_FLOATTRANSPARENT_ACTION is exported, the
beginTransparencyGroup()/endTransparencyGroup() will write something
like "Q 0 0 0 rg" where the Q clears the previously set clipping region,
which is then not restored.

bdf75c7d9bce985ed10a9c41d03420f33ce82142 appears to be a fix for a
previous related problem; this essentially reverts it since it
introduced the current cropping problem.  (Particularly funny is the
comment "force reemitting clip region" since the commit does the
opposite.)

It does not really make sense to me to write something to the page
content stream from beginRedirect()/endRedirect(), because that does not
actually have any effect on the _content_ of the substream, because the
referencing of the substream is only written _after_ endRedirect()
returns, so basically what is written can in the best case cancel itself
out and in the worst case introduce bugs; the state manipulations there
are just to modify the m_aCurrentPDFState following the push()/pop() (it
is necessary to clear the clip region before starting the substream to
avoid spurious "Q" at the beginning of the stream).

Change-Id: I4a5f57b784068bd7d3ba187115444574f7418195
(cherry picked from commit e8062623355fcf3e65beae7f8f5e4d46384141f2)
Reviewed-on: https://gerrit.libreoffice.org/8813
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
fdo#76697: Remove this duplicate and use the UNO constant values instead.

(cherry picked from commit 72b2fafebfc44fa90f08cc198e2fa5fc26154c5b)

Conflicts:
	xmloff/source/style/bordrhdl.cxx

This fixes the bug because in XMLBorderHdl::importXML() the value "none"
was rejected as invalid because API_LINE_NONE pointlessly had a
different value than BorderLineStyle::NONE.

Change-Id: Id81aacc6c594ad25d97f6f6dc578ed9ca16549ab
Signed-off-by: Michael Stahl <mstahl@redhat.com>
Resolves: fdo#75307 discard invalid user data

Change-Id: Id39b51c344004e02d3d5a281ba98721b944468c3
(cherry picked from commit f5b9db43080658201caf07cd646bae4f4f2acc95)
Reviewed-on: https://gerrit.libreoffice.org/8815
Tested-by: Michael Stahl <mstahl@redhat.com>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
resolved fdo#76949 correct grammar is GRAM_OOXML

Regression introduced with ca8ca8c28742879220f3ff88ae0d71c8d69b11cd that
used GRAM_ENGLISH_XL_OOX instead, which is English UI function names
with OOXML reference syntax.

Change-Id: If6b73e85a45e57f6ef281d1edf8e34dec7cb9bb8
(cherry picked from commit 31e4419ac7581aa7864905bcd4ce42e14df6c9bb)
Reviewed-on: https://gerrit.libreoffice.org/8817
Reviewed-by: Kohei Yoshida <libreoffice@kohei.us>
Tested-by: Kohei Yoshida <libreoffice@kohei.us>
Support SmartTagRecognizers again

The XContentEnumerationAccess is at the service manager, not the component
context.  Regression introduced in LO 4.0 with
4381f3dd5ae9e042840a16f69d07267208160420 "fdo#46808, Use BreakIterator ::create
method."

Change-Id: Idb7d38b9c14beea9a9ad347e6cbc8190d7248b2d
(cherry picked from commit d4c8325ea9cbffeff91de49d5e1f1f026be319de)
Reviewed-on: https://gerrit.libreoffice.org/8824
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
Resolves: fdo#73936 make FormFieldDropDowns a real fieldportion

split the checkbox and list and use a field portion for the list.
That way it knows how to line break correctly wrt hardspaces and doesn't hang
when the situation arises.

(cherry picked from commit a52ee51269a47e52d68405caf8507e1abaa6fd8f)

Conflicts:
	sw/source/core/text/itrform2.cxx
	sw/source/core/text/portxt.cxx
	sw/source/core/text/portxt.hxx

Change-Id: I46d73f19ef8e51e7c21c8783ce70bb80d98a784c
Reviewed-on: https://gerrit.libreoffice.org/8776
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
Resolves: fdo#76905 long delay when changing font size from % to pt

(cherry picked from commit aa16ca73260681b19f0be8a58be95ed454580f7f)

Conflicts:
	svtools/source/control/ctrlbox.cxx

Change-Id: I33d72b51536ab96653ccda64c6e058c497289327
Reviewed-on: https://gerrit.libreoffice.org/8814
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
coverity#707971 Uninitialized scalar field

Change-Id: I5c1045253c082a00397cf0f048baee947232c9b1
(cherry picked from commit 4ab06a576313de973ae96787a19215b208737859)
Reviewed-on: https://gerrit.libreoffice.org/8820
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
fixed display of available dictionaries strings

Since commit 9dc57be59d1a8dc17e77f21cbce04e2bb7247dca under
Tools->Options->LanguageSettings->WritingAids "User-defined
dictionaries" the language strings are displayed as
" '[' Language (Country) ']'"
that before was and instead should be
"[Language (Country)]"

Change-Id: Id7e7ef6ab86112c46707f1451a072dfc196aec44
(cherry picked from commit cc658066aec0a0f9589e7f9522c4431b3a3d5e96)
Reviewed-on: https://gerrit.libreoffice.org/8829
Tested-by: Michael Stahl <mstahl@redhat.com>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
bnc#821208 DOC import: fix unwanted char background in numbering char style

Word supports formatting the paragraph parker itself, and we import that
as a formatting at a position after the last character (e.g. "foo" will
have that formatting at char pos 3, which is ignored by the layout).

In addition to this hack, commit
1c22545edf9085b9f2656ca92781158b6b123db3 (Fix issue #i119405: Numbering
text style changed after importing the *.doc, 2012-08-24) added a
SwTxtNode::TryCharSetExpandToNum() hack to Writer core, where in case
such a paragraph marker attribute is set, and the SwTxtNode has a
numbering, then also modify the associated character style as well.

As that commit already noticed, there are attributes which should not be
propagated to that character style. Extend this blacklist to ignore
RES_CHRATR_BACKGROUND as well, as Word does.

Change-Id: Idcb40d37d8688c76fbd61f28428f6e3bc995f799
(cherry picked from commit 5a5d948e230dfea61108452579b68da75706cad4)
Reviewed-on: https://gerrit.libreoffice.org/8827
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
accept proper number style condition != as not equal operator, fdo#76777

ODF 1.2 specifies '!=' as not equal operator in <number:number-style>
<style:map> style:condition attribute. So far '<>' is written, accept
the correct operator.

Change-Id: I6087992ee35fff5c7aa52b7cec2b83b0a78dbac1
(cherry picked from commit dfcc851d65c8d81988843ef31a75b5d30051ddfd)
Reviewed-on: https://gerrit.libreoffice.org/8834
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
Uploading libcdr-0.0.15: Support for CorelDraw x7

(cherry picked from commit 32f301f5a64d8ff7815cf88858fc8a87cb9ad76a)

Conflicts:
	download.lst

Change-Id: I1cc6c6ab39ec27dbf08c2019c7dd7f8f29537520
Reviewed-on: https://gerrit.libreoffice.org/8845
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
WMF import: restore support for the ImplReadDIB(bFileHeader=false) version

Regression from commit f7799c9317cc3187ae8aaedc36f829d478a59e77
(Resolves: #i124467# add check for image data offset..., 2014-03-28).

Change-Id: I71e78aefca2ca5b07f763ec798226b9bb39a5254
(cherry picked from commit 9984807f17593b97778fc31824c50706ea2e826c)
Reviewed-on: https://gerrit.libreoffice.org/8849
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
fdo#76298: sw: do not start up every OLE object on deletion

First check if it's actually a Chart embedded object; starting up
external processes on Windows for arbitrary OLEs is likely expensive.

(regression from 1ba29be90f7141077f2d079d40dffc2efd4f1a2c)

(cherry picked from commit 206848294f686a0ccf4c741d7e92a2314a88ea48)

Conflicts:
	sw/source/core/ole/ndole.cxx

Change-Id: I3c64444b6cf4d4f791cafc77ec1f9b2b0150ad1b
Reviewed-on: https://gerrit.libreoffice.org/8881
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
fdo#74823 RTF import: work around wrong table column width on invalid input

This scenario is not a valid one, Word doesn't handle it, either -- but
the old LO 3.4 parser did. So add minimal support for it to avoid
the regression.

(cherry picked from commit 0a215b9a980e68f899ad548f780bbe5a1fec8732)

Conflicts:
	sw/qa/extras/rtfimport/rtfimport.cxx

Change-Id: Icc2e8d3bf314e9cadda57956668033aa6d092457
Reviewed-on: https://gerrit.libreoffice.org/8871
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
fdo#75772 Correct name of Outline Numbering dialog

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