Change-Id: I4e4d9c9aea5bb9387dbb2e69d94c48f4988c3346

Use correct aspect ratio for the images.

Change-Id: I99c676c8c843c48633b5f17fd9333d0e0af4753f

Change-Id: I1acac06f076a4f8173929a0fe0c0d9eaf6b8d1ff

Change-Id: I64b995c15a83d71aaa6745323141e71cc55cf000

no close on error paths

Change-Id: Ie544bcd6ea7224bee2a092013a589c509d42c735

unused since

commit 17714047
Date:   Wed May 22 06:40:48 2002 +0000
    #99282# CTL - Replaced GetGlyphBoundRect by GetTextBoundRect for drop caps

Change-Id: Ic2a5fdbb0c2f66268c60f86d6596d66ad24b7712

I imagine its deliberate anyway, always has been
this way since 2000

Change-Id: I45fd654aeec2a5c753c38d20febd2f820044bb32

Change-Id: If5dcb4bbd728f7396e19382f85bdf2a3d77a6db6

Change-Id: I15acdaaa810b5ee209764a277d0da5a4d7773466

Change-Id: Ia6a1ee154254e7efc0d787ce92222e80fecfd04e

Change-Id: I16180cae5fcf8dc59614f4ccf33f8745db05e138

Change-Id: I2c3f10894ffe514dbc71cd1dd672685aa8f09a0d

Change-Id: Ia9cb84bb0924915d4611c5f18d2a0d19b4198d94

because get_stack_trace uses rtl_mem::allocate and that throws on a (unlikely)
memory allocation failure

Change-Id: Ic2d0e6ec76eab5cf73025fa4d3199c29eb5b2982

Change-Id: Ic906740ddeab04a9acfee997a31a2249f23de65f

Change-Id: I7fdd4541ac61729878149bd47080e9ffbd43bc98

Change-Id: Ia3bf8a59c38b32a9ed24d21432f95e7141d72072

Again no need to adapt dmapper/rtftok for these, see commit
020f46d1 (Use constants for ST_Em
values, 2014-10-07).

Change-Id: Ie67f7a4d251525b5f8799cf613bea56ad82f7a57

Change-Id: Ia45890892f3a0fa89b4c1f97a4c169de5e25c593
Reviewed-on: https://gerrit.libreoffice.org/11860Reviewed-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
Tested-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>

Change-Id: I6f23bd0e0553b8f6435537b542fc82ee55a64c03

Change-Id: Id4e65908cc73978205bc0858a3a809b882864b62

Actually, we check HAVE_FEATURE_READONLY_INSTALLSET and not
HAVE_FEATURE_MACOSX_SANDBOX, but in practice we set the former only
for the latter case.

We could do this test cross-platform but I didn't bother now. Nobody
uses --enable-readonly-installset when building for Linux or Windows
anyway, I think.

(There must be more places where we could and should check
HAVE_FEATURE_READONLY_INSTALLSET.)

Change-Id: Ie54f436616a1db3119b0bc0148149784127b156d

- problem was hang after replaceall or searchall function
- fix slow performance by looping only selected cols.

Change-Id: Ic0178af33bf381e52584bd4366bff9e128891b64
Reviewed-on: https://gerrit.libreoffice.org/11829Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: Matthew Francis <mjay.francis@gmail.com>
Tested-by: Matthew Francis <mjay.francis@gmail.com>
Reviewed-by: Kohei Yoshida <libreoffice@kohei.us>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Change-Id: I4fd649ee20f76063784cea5f46e42cadb350077e

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

from SvxMSDffShapeOrders.

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

Use gperf instead of ls to find binpath, so that vs2012/3 can be tested
on non-Windows systems.
Output the vcxproj and vcxproj.filters files with indentation and
formatting.
Make some minor changes to improve pep8 compliance.

Change-Id: Ie8ac11ecf75ad170f0756f803c45356685792e5c
Reviewed-on: https://gerrit.libreoffice.org/11797Tested-by: David Ostrovsky <david@ostrovsky.org>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

from ItemFormatMap.

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

Change-Id: I5897a774b8949f336a40096a0727a347bae012ac

Change-Id: Ia2bfaff2a284c2ea40198f1152716860d5963482

tools to correct svg:d imports

(cherry picked from commit f077f99d)

Conflicts:
	basegfx/source/inc/stringconversiontools.hxx
	basegfx/source/tools/stringconversiontools.cxx

Change-Id: I7de1558682990f83e66fdded3d9d30e21e4f97fe

Calling std::list::remove() iterates over all elements...

Change-Id: I46d00217911c1863f70d3ba72dc7099411714471

Originally this used both SolarMutex and an own mutex, then a deadlock
was resolved in 2fe6a4a3 by not locking
SolarMutex.

Since the class will call event listeners without dropping the mutex
e.g. in insertNoCheck(), using the SolarMutex appears better anyway.

With this, installing a BASIC extension no longer triggers SolarMutex
asserts in SfxBroadcaster.

Change-Id: Ib9a2ee491ef53b1a53855af0fc22e863c5e7cb91

The locking strategy in the basic module is totally unclear to me, there
does not appear to be a dedicated mutex for the core stuff callable via
StarBASIC, just a bunch of SolarMutexGuards at random locations;
let's try to use SolarMutex at the UNO entry points...

Change-Id: Ia9c45fdcfb5ffd0a4acc77ef5d2fabfb8743ad38

Looks like they are backwards to me

Change-Id: I20f38050172c1671a81d6ab7de80123ad1703528

Change-Id: Ie00a983cc93736528e16b4244aaf1361536ed9b6

Does nothing useful so far.

Change-Id: I9d288a8b8ab92e01a28c92bb41162af4410e0163

Incorrectly converted in a384b21c
where SFX_IMPL_ONEINSTANCEFACTORY was used.

AFAICS it's the first converted single-instance service which implements
css::lang::XInitialization. That's kind of strange but can do its job.

sbergman@redhat.com:  Three things were necessary in order to not call the
~ShutdownIcon code too late during exit now:

* Move the relevant code from ~ShutdownIcon to ShutdownIcon::disposing.

* Add a dummy <singleton name="com.sun.star.office.theQuickstart"/> so the
  service manager will eventually dispose the (single) instance.

* In
  cppuhelper::ServiceManager::Data::Implementation::createInstanceWithArguments
  do not shortcut updateDisposeSingleton in that odd case of calling
  createInstanceWithArguments on an implementation that (effectively) is a
  singleton (as otherwise the service manager would still not dispose it).  It
  looks to me like that "return inst;" was an inadvertent leftover in
  874c4818 "Simplify service manager's tracking
  of singletons" and wasn't intended to serve some subtle purpose.

Change-Id: Icd4d3168ec0bbb820b17ac321fe897ac9f9ce7fc

causing m_aDataArray to be cleared, so the rItem the result of GetString
is being assigned to is invalid

Change-Id: I1dc30d675233ddc53234bdb5349c5f374b036ca8

Change-Id: I52eb3400769999d7f554c3bdb8746f65b7990388