#i124421# disable generated type_info for the OSX64 uno bridge

When the dynamic loading of the type_info symbols failed the UNO bridge
synthesized type_info objects itself. The synthesized ones trigger the
crash observed so we disable their generation and handle the result
gracefully.


git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1582359 13f79535-47bb-0310-9956-ffa450edef68
#i124421# force the availability of type_info symbols thrown by the ucb module

When exceptions are passed around in uno::Any types to be thrown later it
was observed on OSX64 that the type_info symbols of these exceptions were
not available anywhere. On most platforms the UNO bridge would synthesize
them by emulating how the platform's toolchain would do it. Forcing the
emission of the type_infos by the real toolchain is much better than
second guessing and reverse engineering its operation.

An even better approach would be to have the ucb throw the exceptions itself
instead of wrapping, rewrapping, unwrapping, etc. them. Once this is done
the dummyThrower helper function is no longer needed.


git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1582365 13f79535-47bb-0310-9956-ffa450edef68
#i124516# handle bad surrogate pairs gracefully on Windows

When running into invalid Unicode surrogate pairs the text layout code on
Windows ran into massive problems like crashes. This change detects the
situation of an invalid surrogate pair and falls back to treat it as
a simple character instead of requesting a complex glyph fallback.


git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1582374 13f79535-47bb-0310-9956-ffa450edef68
#124311# merge fix from aoo410 branch, correct system requiremnts in readme, new 10.7 (Lion)

git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1582389 13f79535-47bb-0310-9956-ffa450edef68