With size 1 every ImplFontEntry should be immediately deleted, which
makes tools like valgrind and drmemory more useful.

Change-Id: Idec40c7cf7d927146f23830a42b3464c1675207f

Both valgrind and drmemory complain about this in
SdExportTest::testSwappedOutImageExport() via
SfxOleThumbnailProperty::ImplSave().

 Syscall param pwrite64(buf) points to uninitialised byte(s)

 UNINITIALIZED READ: reading 0x0455b1b4-0x0455b1c8 20 byte(s) within...

It appears that the stream writes out everything up to the seek position
anyway (otherwise the size check wouldn't work, with sparse files)
so make sure it's all zeroed.

Also fix SvMemoryStream::ReAllocateMemory() to zero it.

Change-Id: Id86dfa65ef6f7d1bba4810f121e01473c5fcf4c7

Change-Id: Ib77ce1b95db2dc4396f4fd2fdcff4c0344b20c9e

Change-Id: I27bb289288d319a93201e9c3d703114924ca258c

Follow-up to 34700400; this fixes sw_ww8export
unit test on Windows.

Change-Id: Ic0c3228efb59a182e1562b73117418cd8b5e6017

This reverts commit 5191fcb1.
Earlier, better fix was 831c69f9

Change-Id: I0d1c988aad308435542dbd381fcf6bf7e1af6290

Change-Id: I83f45260158f5282b857458046d2e324be85a7b5

Change-Id: Idc3c74505d84a96bb5cc6713a95ef2fadc267ea8

Change-Id: I358fe0f3dc11939269f58b345489621b0ad25797

Change-Id: I695260d6d0c727c3ba7a67886e535569292b15e5

Change-Id: Iefe943794e005f03b2a6ea5fc642b8c3d21b3334

for penance, introduce a unit test

Change-Id: I2c40285732be665e179c477e6e7603aa6f8be5d7

introduced in commit 4aed1c6f
"replace boost::ptr_vector with std::vector<std::unique_ptr>"

Change-Id: Id16921f212128d34835a4c0b9facd18cb264da62

which just serves to make the code harder to read

Change-Id: Ib681aad99180df26b1cf3f4e23324dc5a86cc299

Change-Id: Ia7b5dce6dbdfd3cfd066003762f449b8bf1ff41a

Change-Id: If18f530f613e7cb9d0c8f0989752f31178c97dcd

Change-Id: I3b33529a37174682e68be897a77b2736133b6ac6

Change-Id: I3cdb647e1a057be5bb4b32d119ee5bcbbedf7473

no version bump but B_USERTYPE defined

fix test from commit de26ef85 that should be nMaxRecords

tested full round trip on password protected document (ie. use binary storage)
master --(0)--> master --(1)--> libreoffice 4.4 --(2)--> master --(3)--> master

(0) in master, User type supported, big module supported
(1) in libreoffice 4.4, user type not supported, big module supported, no loss of code
(2) in master, user type not supported, big module not found, no loss of code
    it is OK as libreoffice 4.4 saves to LegacyVersion
(3) in master, User type supported, big module supported (all is restored)
    it is OK as module was saved with CURRENT_VERSION (see sbxmod.cxx)

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

Project: help  bce98cd0f5446b99a1258eee3138c13469ec510a

Add example to Basic IDE Options help page

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

Change-Id: I6c42e6a9ead90ed6fad2f289cd686a72cffa0c2d

Change-Id: Ib7df410c79dcdae343d4e7b250aad606fd777526

Change-Id: I65ed5979d35d8739367294a71620782b832cfd71

Change-Id: Ib4e7f4f71494abd654a70cf8ba8b0ca0afcd7df1

Change-Id: I22f995b905e7abf1451a0636083bf19b3f2d9bc4

and remove some dead code

Change-Id: I6a42dbaea5053b4aa3c47b3f154410b05f32dfe4

and remove some dead code

Change-Id: I608ed684fafb33390d869f7ebd4000c53d7fb28d

Change-Id: I236c1a35534c3b0a8461caffbaf852e9bbbd621d

Change-Id: I885694b2f7c950a292dd903952c5d298b9d0df9f

Change-Id: I53b0a7a9875a3ebcca915c8f2d8c53face6f9509

Change-Id: I8949a92792df892b7f360e6b9979c8f61c702ce3

Change-Id: I9eba6d3f5335060f697ad53e7e2360ef2142609f

Change-Id: Idd4ecc2f9f566b2d1fa0127dae12fefe1e4479e8

Change-Id: I3f75ad585ca288f0369e91dd5bc90151270346dc
Reviewed-on: https://gerrit.libreoffice.org/18048Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

with the variadic variants.

Change-Id: I01909ee45c31d17356e13b1ff2430440daff9aa7
Reviewed-on: https://gerrit.libreoffice.org/18146Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: I8f005d72c73d7e058fdb06351e8bc075d049d0f7

Regression from commit 7d9bb549
(Related: #i124638# Second step of DrawingLayer FillAttributes...,
2014-06-02), the problem was that the new
CTF_PM_REPEAT_OFFSET_X..CTF_PM_FILLTRANSNAME range's values overlapped with the
existing CTF_PM_HEADERHEIGHT..CTF_PM_HEADERGRAPHICURL range's values, so
when the new code in XMLPageMasterExportPropMapper::ContextFilter()
tried to tweak header repeat offset properties, it actually disabled
HeaderBackGraphicURL instead.

Change-Id: I9c2700fa71a4ef2a813ec671049ee9d98171b57e

Change-Id: I349e1b9e3ea81c0684c6234497b6d44b47666b09

Change-Id: Iff591fb7cd434805998fdd14b94c4dd9654ba55e