Change-Id: I1dd85a7b1236cfebd5e653fe6d329968e556364b

Change-Id: I1bee29ddcef66cb38ef2619507ad66c886f6f20d

Change-Id: I12cb17c5b357d966e7a11bdeb69d930bcdc8ab22

Change-Id: Ic3b355e732bcbecf020720752aadd70e0722b6f0

Change-Id: Ib695a664356baf288f74fcefac35927726def0c7

Change-Id: I2170e8fd9ef5ca0556545cb3f656a0e1ba49f43b

Change-Id: I74f1a032ebce8e4fa13d4afd7f520bbb367b2df5

Change-Id: Icb95d60a7f786ee75ea1904cfb7292e51eb607cc

This makes tools pch ready.

Change-Id: I8d5d5fcbb417f3790749aeb9d9c947f739ecb30f

Change-Id: I66b3dc79998de018eae1c7eff8ce23f95e3c3f33

Change-Id: I8a9a8c56b91783288e2319ad3a5e9803ab5562d0

Problem Description:

1. On 19th  May windows daily build
[Build ID: dd0f8447, TinderBox: Win-x86@42, Branch:master],
if we RT document, RT get corrupted due to the exceeding the limit of extend height & width.
2. As per ECMA standard, extend height & width is of type long, but MSO only
support int32.Hence added code changes to check the same.
3. On 20th May windows daily build
[Build ID: f3a46244, TinderBox: Win-x86@42, Branch:master],
if we RT document, it get corrupted due to exceeding value of posOffset.
4. Added code changes to make sure posOffset value is within the allowed range.

Reviewed on:
	https://gerrit.libreoffice.org/9424

Change-Id: Ib0b55314f54c51f39a492485992356f71eb062e3

Change-Id: Ia045472386c82369206bfb06dbc8f7a5bde60510

Change-Id: I5b3e785ce50b5959d64c855869533a310e9c277a

While at it, make it use SAL_INFO instead of fprintf.

Change-Id: Id4018819f8f790bef219e5aca3b6bbb5f6acd6aa

Originally a Field began inside a hyperlink but ended after the hyperlink.
This causes the corruption in MS Word.

Incremented the field count if the field is added for the current new hyperlink.
Added another variable to store the Field-Count from previous hyperlink.

Added UT for the same.

Change-Id: Id3c3bee1c8ed9c0755f8fff7efd5d1c5662f2c82
Reviewed-on: https://gerrit.libreoffice.org/9421Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: I711621c89e8f75d4450867e303ccdc8017bcd9d7

from 196396ffc72bbb1e4f9bbc8ff83432e22bf638af:leak-sanitizer/leak-suppress.txt

Change-Id: Icc7bab46de7a8e63ce149fd0277283f267fb2931

Change-Id: I8b2ecef11362c0fc1dc2b76780140881e769bb89

Change-Id: Ibee9d8f00008dd0a266db276772d48deb0bd9d18

Change-Id: I71c7fe027262305893d8eabee94a726f4aa909d6

Project: translations  b31a57455b1bf9dcffd2cee0a4c79c4f6425dd6c

This time we did preserve this info, and we should not.

Change-Id: If2ddd7a266cd7da5642dc234411ce34e94bd3384

Change-Id: I102160cb6fac41f5ba3caa5cb947aebbcd62681f

When we have <w:br> tag continuous like in the following cases...

    "Title: Superstition\v\vComposer: Stevie Wonder\v\v"
    or "\vLyrics: \v"

    where "\n" is internally replaced by "\v" LO.

    Before text "\v" or after text multiple "\v" is not preserved.

Conflicts:
	sw/qa/extras/ooxmlexport/ooxmlexport.cxx
Reviewed on:
	https://gerrit.libreoffice.org/9420

Change-Id: I2a6d0a7d2382dfbc2f0ab04f150653c9b17bbfd1

In a hyperlink, extra field with fldCharType="end" is getting added
even though there is no begin and separate fldCharType. When hyperlink is
closing pageref was not set to false. Due to which LO was adding extra
end fldCharType.

Change-Id: I0f54ab03c38cec2888cf9a1638ec5435da90099c
Reviewed-on: https://gerrit.libreoffice.org/9414Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

- Normally if there is a case where text/shape is overlapped with (another)
   shape then LO used to write the text and the AlternateContent in the same run.
- This is supported in MSO and there is no visual difference.
- But in case if the SdtContent(with text) is overlapped with the Shape then LO
   processes sdtContent as a text and ends up putting the alternateContent and the
   text in a single run. Ultimately it includes the entire run in a SdtContent,
   which is incorrect.
- The fix checks for the aforementioned scenario and puts them in a different run
   and also restricts the sdtContent being written in an invalid AlternateContent.

Change-Id: I36f4cdb1b583523dd8f717ae094bdf09c7a61f62
Reviewed-on: https://gerrit.libreoffice.org/9374Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Replaced OSL_ASSERT with SAL_WARN_IF, OSL_TRACE with SAL_INFO

Change-Id: Ia2283c09ac702558fe6ad39e963b0f401ef31de0
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>

Change-Id: I044f12c4b7b28963d6d491d5e5850ddb59a564c4

Change-Id: I7769625289d8bf47fe5905dfb91d3bce9e0f5c85

Only consider base declarations, not overriden ones, or we warn on methods that
are overriding stuff from external libraries.

Change-Id: I08791c96f7adba5997ad237a98e7c08a759042ad

Change-Id: I8afab424c051453005432c5291af49eb208dd22c

Change-Id: I5707aea9965e0d288d4a0e742f5d3cccf08107eb

Change-Id: I963419baec24d7599ddb3e481738cbe6ec4e0a69

Change-Id: Ic88b22895c2eb4144d31f22a0f7bc98971873262

Change-Id: I465e23dbe1d84a411c65500875a8821a116ecd2b

Change-Id: I76da768e035176c6469d9473364e9e2c9086ecae

...as reported by AddressSanitizer, where src/core/CLucene/index/IndexWriter.cpp
initializes IndexWriter::MAX_TERM_LENGTH with the value of
DocumentsWriter::MAX_TERM_LENGTH before the latter is initialized in
src/core/CLucene/index/DocumentsWriter.cpp.  But turns out that
IndexWriter::MAX_TERM_LENGTH is completely unused.

Change-Id: Ica01186584ec05a989a13dc58823f4751e8724e2

Change-Id: I9251488743ec3801367600455ef9a22ad876d2d3

Change-Id: Iaa80388952ac38a088874629688d9cf8a5fd456d