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

Change-Id: Ie5ccd62608c0643e3c8f019aea136ba74b282274

Change-Id: Ia980054437394ef48f7df655411f81d20b9cfa32

This reduces external link update time by 10%.

Change-Id: Ic14d9ea7530818f839330a2004f6aa67ef1e831e

Change-Id: I18520837f8d25103bf8482a0204b8a7b7740feb1

Change-Id: I5e34f4d7561ef7f4f7b8b3b4d7d06cca072831c7

Change-Id: I0ae2f44b89b0db915e78a9b07835000e843d016f

Change-Id: I983127828b28c72dd12d4778b88051964e9bceaa

This way, even after the loaded doc shells get purged due to timeout,
we won't reload those external documents from disk again.  One caveat
is that we currently don't pre-populate empty cells even if they are
referenced by the host document.

Change-Id: I1de2987836bf2fc5d9d7044b406fb99faa534164

Change-Id: I88b205d36eede5e63af46f8581896d980b6aa27d

Import especially when we have a whole bunch of large-ish documents open
in the background.

Change-Id: I614e6daab3481c09dae47c8407497d77aec40480

To prevent collision with the timer wanting to purge the doc cache
while updating external links.

Also, show progress bar, and make the timer interval and the document
cache life span longer.

Change-Id: I325984c8fa68425a2621cf8f9c016463291afc89

Rather than just clearing the existing caches and loading the external
documents on demand as the formula cells gets re-calculated.  This has two
advantages: 1) when the loading itself fails, we can keep the existing cache
rather than turning all affected cells to error cells, and 2) this prevents
on-demand loading after the external linkes get refreshed, which can make
scrolling very slow & painful.

Change-Id: Ie8243f6f94c5e477964413ab83f6b4b746fe3220

Change-Id: Ic309dbcc49a423bce10e9ea711e8ba0702552816

breaks the build otherwise on the baseline

Change-Id: I7a357bc9b541c86746ce3000af429ee024efeec1

The fun thing is that with the (only) call-site to ReadAsynchron in
PNGReaderImpl::ImplReadIDAT (vcl/source/gdi/pngread.cxx) passing in rIStm
references to stack-allocated SvMemoryStream instances, mpIStm could point to an
old, destroyed instance from a previous call, but which would have been located
at exactly the same stack address as the currently passed in rIStm, so the wrong
mpIStm->Read call would effectively behaved exactly the same as a correct
rIStm.Read call.

This went unnoticed "since the beginning" until AddressSanitizer's
UseAfterReturn check came along...

Change-Id: I7c75ed2d36a4c24c111d88eff647816bd2c5dbca

...(which can be called multiple times in a row).  But which actually looks
wrong...

Change-Id: I2e4914e6fed8ced383e430699dd462add9da8c08

Change-Id: Iebb19951efa81817793a155164862076d1198e6e

No need to create cached versions of stringified sheet tokens for
a given grammar at great for every formula that we compile; defer
until use. Is this a large cost on save ?

Change-Id: I8058ed564dbdc00ff45c02cb483c1a20a48af272

Change-Id: Ia394ff00421f495757cc2ce55e7b91bfebe715eb

Project: translations  b1ee9c9e1542b856cfe2412c6dffeeb5a353810a

debian packages don't cope with release number of 0, so use release 1
for debian master/dev-packages

Change-Id: Id91926322d13bddad3a39faccfee4e131d8956b0

Change-Id: I2714b1f1dadc74f8501203bc8b0722c56c9c5fb9