which is used to parse Microsoft Word OOXML documents in case of unknown XML
elements

(cherry picked from commit 22e33484)

Conflicts:
	writerfilter/source/ooxml/OOXMLDocumentImpl.cxx
	writerfilter/source/ooxml/OOXMLFastDocumentHandler.cxx
	writerfilter/source/ooxml/OOXMLFastDocumentHandler.hxx

Change-Id: Ibcd3e808abfb35291bb04aa10190a7800f0837fa

Change-Id: I582a841ea3b2a882cbdc1556058b007a8667024a

Change-Id: I7312d94f90758d450a69410819c5e8c142756a47

gb_LinkTarget__add_internal_headers was used only for sdi headers now
anyway, hopefully for no good reason.
One headers target is enough for all.

Change-Id: Ia01fb7a0aac7f72915448424b3393ecd9ba0f8f5

Change-Id: I549bba35a983a61aedf6f0ff9709b0efc14a603a

(cherry picked from commit cdf48cfd)

Change-Id: Iaa62acc4901c3edd31d0af7c642327dddf07f562

Change-Id: Ib2f267b85b04be91b7e9091613b0665a1eea3f01

Change-Id: I68410bc1a8b77877b07f60e6ace0f54c255de95f

Change-Id: Id63520c60bd4c7f44c271fdb2a832627c42b8738

This reverts commit 9ff0ee49.  Whatever the gold
warnings are exactly, this is apparently not the right fix.

The change to openssl/ExternalProject_openssl.mk caused crashes when LO's
libneon.so, statically linking in LO's libssl.a, started to export symbols like
SSLv23_client_method as global, competing with the same symbol from a system's
libssl.so.  See the mail thread starting at
<http://lists.freedesktop.org/archives/libreoffice/2013-June/053119.html>
"strange crash in SSL code while opening some documents."

Whether the change to expat/StaticLibrary_expat.mk caused similar problems is
not clear to me, but it is probably best to revert both to be on the save side,
and see what exactly the gold warning was about and how to fix it the right way
if it ever shows up again.

Project: help  ed02574e293074b182982a4512884a6f2d7bcc5c

Change-Id: I892fd1a4b8085c1f7c9651d15015fc220876ebee

Project: help  62d083404f888fa33ad1264c59b46ae8a6278e91

Change-Id: Ie0aed71457891e58916d064c9a59d5927c31f1f7

(cherry picked from commit 7fb9e99f)

Change-Id: Ic4dd8c7c5d964fce9ed971c9a5a337a7cbb04fcc

in Line/AreaPropertyPanel

(cherry picked from commit 2890568e)

Change-Id: I6436b165a873e6f79af29690170231af939fcccc

This is similar to a996678e. If we have
both a background object and some clickable field to select, we should
always prefer the clickable field.

This time, the problem was to click on a clickable field, when the
cursor was in normal text and we had a full-page background object.

Change-Id: Id25036d8cb2ddf62011c22bfc50844b793b942bd

Change-Id: Iaf0e1dccf1af3bcec1057e42934d2931ccebfd32

Change-Id: I3b5e3a8bf4bbecf6bf697b91c9a16ec19045bfdf

Change-Id: I2b78c7b714ff064f2f1b8a8eb161e5e2ae121eee

Change-Id: Ica7bd2d6b395d42d575660991ec74ecb2b744473

Change-Id: I64fc36b38be59c909aa96a9faf876232caaac182

Change-Id: Ib2578cd94c74f171b58f3478d758221593ee5523

Change-Id: I4820830f24c8a9a6d9ec3ad79df51bb2ac4f1e4d

Change-Id: Iaf7c4bc438147a283e6493598d250c9b53dd6fc0

Change-Id: If995a2cf00e2ced618ad1a1a68d093eb163ee27a

Change-Id: Ie2b52f66c02f395d45fe24bbd2c3d897c7335add

Change-Id: Ie2162b71e4e9de9fe24ce54815e5139774bb2ec0

Change-Id: I00c753f71460bee9f2bce3af35b352a25a3b8484

Change-Id: Ic9e049b6b79a8ae3777d8b2a6e918289445c21da

Change-Id: I87bf28e1d6db2afe5ffa095cbf9181602ec9fc3f

Change-Id: Id10f827ef70a19a6261abea5c1b6c835b8bee701

Change-Id: Idb78cb18ed7718996628233dfb546eb1f6f345c1

Change-Id: I7961ffd978cb02c62be176a0afe931959b7d8f1f

Change-Id: I8c0a97372f0855543d6207adb0abaa4cc820aabd

Change-Id: Ia0ff071a5676f27d39175e30d7c5f472e32c99b3

Change-Id: Id6b8f4ed6df14bd80a7937001ec1cfb98acd7f52

Change-Id: I9edf21919322af22e323b48009e934d70766353e

Change-Id: I403cad8ce1953d2c8e8948a94a688519525bbbc4

Change-Id: Idb263ad369d2dad4fe4de924f2b2404a0fcf62d3