Change-Id: I9ba0b27924d1698bad2c34da75fff57f75a737f0

Change-Id: Ica3430e75c91ccf4861fce660c45b90c5584fb9a

- in the libbiblio component the frame is already created, and a frame
  that is loading is vetoing a terminate
- thus move check to sfx2
- use the fancy svtools::RestartDialog

Change-Id: I500aaeac44d52969575f50f6b79d0c07a08c977e
Reviewed-on: https://gerrit.libreoffice.org/1207Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
Tested-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>

Corrected types and grammer errors in comments

Change-Id: I47ce77a8d36d71677720be6dd80594ec76970376

Change-Id: Ie42b169437c89d0d94f6749bee21301fa44b98cf

Change-Id: I061dc4ee8c8fb5b369e3ed78f0fba136ef8b02d0

Change-Id: I49e9d40d942dd7a23bebaa4783b0ff59e06890b0

Change-Id: Ia127816f994f7ce6fc7230a0a7dacaa7396ba825

...so that e.g. Fedora 17 does not require installation of libpng-compat package
for old libpng12.so.

Change-Id: I45cf3928b30dbbb815f70cde1972dc4972007c05

Change-Id: If1aad98965a90ac6b2e5488f21fe0d84c9b4af47

Change-Id: Iebd0054605ace7dfd15ee106be6f594ea1e7e0c6

Change-Id: I0fca18232b31f031312f49b8232f0ddda099802c

Change-Id: I44fadc907e5d626cc1912a3d8a82724702ad0462

Change-Id: I69e343a7cf64ce888fc508a27ca316a9c85093b4

Change-Id: Ife2f52b70bd40a8f5c7582b9bdb7b19dd8c354af

Change-Id: If543da8dcd0b0c7a0c155ef08cbc67e1d3905b90

Change-Id: Ieb6b590060b1ca7a497049e974909c9661f1cc14

Trust more the cached colour hex then the colour index

Change-Id: Ica5917c94de4c7bb2a5be61c6b22f06807be0742

Change-Id: Ie9e9baf42c93353a68ef35b456cd621bf42344c5

Change-Id: I48b549ab93dc3b937e00f6f35185a6c1c4327bcc

Change-Id: I7ffc13167f5ecbfe3afab6451e1ef52e81130d48

The following things still need to be changed:
* don't use virtual method in Window
    * Use a WinBits flag for it
* move all the dialogs to it
* fix the ugly hack for range name dlg
* fix all the uncommented code in winproc.cxx
* general clean-up

Change-Id: I2a8cfc1c4abf591878b11aa4829a9ff910540eff

This interface has been deprecated since OpenOffice.org initial CVS
import.

EXISTENCE: published key "/UCR/com/sun/star/util/XSimpleErrorHandler"
exists only in registry 1

Change-Id: I28b2a9dd0180994c077d960bf932fbdea0f282c4

This interface has been deprecated since OpenOffice.org initial CVS
import.

EXISTENCE: published key "/UCR/com/sun/star/util/XCancelManager" exists
only in registry 1

Change-Id: Ibc67f79b4664f8ff9aadacdd36cd8e80c9ff477c

This interface has been deprecated since OpenOffice.org initial CVS
import, and there does not appear to have been an implementation of it,
though strangely there was client code using it until 2007.

EXISTENCE: published key "/UCR/com/sun/star/util/XArchiver" exists only
in registry 1

Change-Id: I8efa29a3d375d7c5c77ae47592b23bec4072d7a0

This interface has been deprecated since OpenOffice.org initial CVS
import.

EXISTENCE: published key "/UCR/com/sun/star/view/XPrintPreview" exists
only in registry 1

Change-Id: I995b7b4fbbdac5582e015daf11d4c644abc53b73

Change-Id: Ide652d073edc3321995b787b01ea9c0bf1920827

...after reading platform makefile because at least python uses platform
dependent gb_PYTHON_PRECOMMAND.

Change-Id: I894dfd56b4a96828556f657ae63c6f69eebdea0b

That $(shell find...) is now entirely pointless with python3 in
tail_build; depend on package instead.

Change-Id: Iacc8a7d201f8ec2e41adf3e2351a755e955c0997

Change-Id: I9ee40fd845aa6af045e49fa4f69165d405ef32c8

... and derived com.sun.star.util.DiskFullException.  These exceptions
have never been used since the initial OpenOffice.org CVS import.

EXISTENCE: published key "/UCR/com/sun/star/util/DiskFullException"
exists only in registry 1
EXISTENCE: published key "/UCR/com/sun/star/util/FileIOException" exists
only in registry 1

Change-Id: Id3a1b9e43350b15b90864628dc2dbf77027d64a8

Exception specifications are useless for production code, but make
for useful assertions in dbgutil builds (on platforms where they
are enforced at runtime).

Because we do not have API tests that exhaustively trigger all
documented error conditions, much less the undocumented or wrongly
handled error conditions that would cause the implementation to violate
its API specification, there is likely some benefit in having these
runtime-checked specifications in debug builds, in the hope that our
various tests which may incidentally call various API methods, or
general soffice usage, uncovers these bugs.

Also, there may be some benefit to making API implementers more
aware of the exception specifications, to quote Stephan's mail:

 To be able to programmatically react to an exception raised by a UNO
 method (which is the raison d'être of non-runtime UNO exceptions), the
 specification of that method must document the method's behavior with
 respect to raising that exception, and any implementation of the method
 must adhere to that specification.  However, with that part of a UNO
 method's interface moved out of sight of a programmer writing a C++
 implementation of that method, I fear that adherence to specification
 will degrade in practice.  And that negatively affects an area where we
 do not shine anyway: reaction to errors.

This partially reverts commits:
0295bd6b
155cd09b

Change-Id: I9c7664c9f1b238f4f9501aacb065981236949440