The standard Boost convention is for them to be called libboost_date_time and
libboost_system (with apropriate suffix then depending on type).

Did not touch the libboostthread library we build for Windows.

Add the ax_boost_thread.m4 file for completeness and possible use.

Document where the ax_boost*.m4 files come from.

Change-Id: Ib49bee71398d62c9760a1f8fd5c46be9f3400430

Change-Id: I88006cced5975fc0748b33094ae39197daba49cc

Change-Id: I66447ffe1a5f364377b80756f6c08f6986ce4eef

This reverts commit 4190fd92.

This reverts commit 9ae9b2f6.

author:	hanya
(cherry picked from commit e945b491)

Conflicts:
	scripting/source/pyprov/pythonscript.py

Change-Id: Ia019a737c5f80d3af9fc50aefcda6f5b00987513

Change-Id: I4ec9444b3ad0d243fda0d93547f000cb7296c0bc

Change-Id: I122254532dfe8ecd9c3118622bf24b50f885a0f6

Change-Id: I95472eb49975861721f5bd6e174b7cb05defe203

Trivial reproducer:

Dim Dlg As Object
DialogLibraries.LoadLibrary("Standard")
Dlg = CreateUnoDialog(DialogLibraries.Standard.Dialog1)
Dlg.Execute()
Dlg.dispose()

Regression from 6c61b20a.

Change-Id: Ia62778c6d94f54e6097a307701e5c81be847665d
Reviewed-on: https://gerrit.libreoffice.org/4023Reviewed-by: Miklos Vajna <vmiklos@suse.cz>
Tested-by: Miklos Vajna <vmiklos@suse.cz>

There are two problems:

1) The classes derived from SdrObject cache their SvxShape, but do not
   implement impl_setUnoShape().

2) There is a lifetime issue in association of a SdrObject and its
   SvxShape. SvxDrawPage::CreateSdrObject not only creates a new SdrObject
   for a shape, but also inserts it into the page. At this point, the shape
   has not been attached to the object yet. That means that the object
   creates another shape at one point during the InsertObject call,
   which is then destroyed again. But reportdesign shapes own their
   objects, which means that destuction of the shape causes destruction
   of the object too...

   My first idea was to disable the insertion in
   SvxDrawPage::CreateSdrObject, but it has been there since the dawn of
   time, so I did not gather the courage to do that. Instead, I put in a
   hack to allow to skip the insertion.

Change-Id: I888a54067be1934578434d8b476a13a7ff8d02b3

Change-Id: I701d12cf8f672824d7cfca1e995f02040fdd3095

This change reorganizes the styles by column ( and by row ranges in that column )
so we can apply ScAttrEntry entries directly via Document.SetAttrEntries(...) this is
what the binary filter does also.

Change-Id: Ice1130d7afccf0be77db24a12f2515eca9c88713

Change-Id: I162574ccf28c88c379e7cc3f88cfe83bc13dc5d4

The library names used in these pragmas dont match what we build
anyway. Whether that should be fixed to conform with "normal" Boost
usage or not, don't know.

Change-Id: I37cb3ff7b340f3362dd7b0fb18ab22188ba54cf6

MSVC generates the warning "user defined binary operator ',' exists
but no overload could convert all operands, default built-in binary
operator ',' used" when iterators from newer Boost are combined with
comma expressions, as in for() statements. Or something like that.

Change-Id: I3225d07ad0d1e05f4deeb784cf2ec081748b1ab4

Why do we accept fuzzy matches?

Change-Id: I5ed2e4f9aae873f701e8276751b3c25ce8d93879

Change-Id: Ibde92f39ac53ee897ee90953b7f60129ba49bd97

Change-Id: Iad3f984722be648a64490976933e9b2c2b950bdc

Change-Id: I7a2bcd802ad9316696398a2e176dc03ea25baed1

Change-Id: I2eefbca1ef986219f04504cba4ca09a22972e8cb

Modify our patches as necessary to match the updated boost sources. Drop
patches for which corresponding (or even identical) changes already are
present. Add a new boostsystem static library and use it in two places.

Change-Id: Ib59558feb56dab87a69c91b38caca8e7a9e9a22e

Change-Id: Ia7f3c2e774ece3cdc35a3a6d220d0eb44e5ad0f9

Change-Id: I708f7eda90d04d736f3798275c2edddcef460ee8

Change-Id: I0dd6730ac3bef95843de25d6813678273cf09832

Project: dictionaries  52fe3741bea0532f8c87f0b9f5dfa5fa367b2fd1

Apparently this second mnXOffset is not needed, further more it breaks
some old Microsoft fonts.

Change-Id: Ice033cb6bcb3f1bdfeef31a8406a7a2e5487da97

(cherry picked from commit 75833fdb)

Conflicts:
	sdext/source/minimizer/fileopendialog.cxx

Change-Id: I164cc6d9916ddf9dba9da273b5181e5728127292

Reported by: Terry Yang
Patch by: Jianyuan Li
Review by: Andre Fischer
(cherry picked from commit 89542017)

Conflicts:
	filter/source/msfilter/msdffimp.cxx

Change-Id: I994a2b14877c4e291d622665ec3f4a8ea9f3041b

(cherry picked from commit 4b0aafb8)

Change-Id: Ieae8e44fe147309cc3ff447a6dbc375d1b2f34d0

Patch by: Jianyuan Li
review by: Andre Fischer
(cherry picked from commit 0ecc381c)

Conflicts:
	filter/source/msfilter/msdffimp.cxx
	sc/source/filter/excel/xiescher.cxx
	sc/source/filter/inc/xiescher.hxx
	svx/inc/svx/msdffdef.hxx

Change-Id: Iac7282e50fd86244381ca174ba3f906aab89c7d9

...originally introduced with 8da92842 "Remove
RTL_CONSTASCII_(U)STRINGPARAM in ucb(ucp)," leading to "IsFolder" not being
properly set in the WebDAV UCP, leading to failure when saving documents.

Change-Id: Id2cc98582c9feffaa501a68069cd606fb420fd29

The WebDAV UCP uses https/davs URLs that may contain a userinfo (cf. RFC 3986)
part, and INetURLObject does not support that (in accordance with RFCs 2818 and
2616) and thus creates an empty INET_PROT_NOT_VALID INetURLObject for such a
URL, leading to failure when trying to save a document to such a URL.
(Regression introduced with 966d20e3 "CMIS ucp:
write documents back to CMIS server.")

Change-Id: Ifd396852b211cab1d29575da7fccb32306479f93

Change-Id: I443367fc355a8fdea3156f85dde65cf43795f1bc

(cherry picked from commit 164d3096)

Change-Id: I29956f976e7ac38a9d06d973bb2b3d2d06e1e341

Text Animation properties to "As one object" and check "Animate attached shape"
option

(cherry picked from commit 897637ec)

Change-Id: Ifbe4f6dbbaebde7afc2d800652dca731ba1c039f

Patch by: Steve Yin
Review by: Andre Fischer
(cherry picked from commit 241c9736)

Conflicts:
	animations/source/animcore/targetpropertiescreator.cxx

Change-Id: Ic81ff35a5a31ba5239510e85c17bb4a261d57b6a

...in commit 6c61b20a,
    "Convert awt::UnoControlDialogModel to new style"
I added an attribute "ResourceResolver" because some of the client
code was setting it using the property interface.

It turns out that this was a bad idea because the "ResourceResolver"
property is doing some very interesting stuff, so revert that part
of the change.

Change-Id: I62b890e60164e005867ced49c3e407a49ed09441
Reviewed-on: https://gerrit.libreoffice.org/4013Reviewed-by: Miklos Vajna <vmiklos@suse.cz>
Tested-by: Miklos Vajna <vmiklos@suse.cz>

Basing this on anchoring is wrong, as SwFmt{Hori/Vert}Orient seems to provide
everything. Also try avoid hardcoding position if possible.

Change-Id: I880bc5c3eeabdde9e52c0c16d1033e44e203a8a3

Apparently the top/bottom line of text alignment in writer is backwards
compared to all others, while alignment to the top of a page puts
an object's top edge at the top of the page, top of line of text
puts the object on top of the line (i.e. bottom edge of the object
at the line). The handling of NS_rtf::LN_YAlign suggests that swapping
bottom and top in the input filter is the right way of handling this.

Change-Id: I916c8ea0f2fd00de3e17b16b31433c9b6ba92e64