Change-Id: If3d9f6272031e08ab228cfa58963d60ceede2498

Change-Id: I7841eee5b66a118c52258c0226d73a1139a0df9a

Change-Id: I1b79005d9c4e32325b8dadcc4f805975d6bf2727
Reviewed-on: https://gerrit.libreoffice.org/21103Reviewed-by: Andras Timar <andras.timar@collabora.com>
Tested-by: Andras Timar <andras.timar@collabora.com>

I.e., don't try to create auto-layout for clipboard pages which
don't contain one; don't resize objects to text.

Also, don't invalidate items that are equal to defaults,
because explicitly set items are not the same as absent items:
pasting an object without an item makes the property to inherit
new target's default, while when the item is present, the default
doesn't apply.

Also, don't consider selected state of the page while stringifying
- this makes selected page string to differ from not-selected
clipboard page.

Change-Id: I172e03e1a8c428e5fcae3a116cc9ad8de79f1a87
Reviewed-on: https://gerrit.libreoffice.org/20871Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Andras Timar <andras.timar@collabora.com>

The testcase for tdf#69640 includes links (relations) to external
pptx files. It demonstrates two non-fatal reasons for failure
opening OLE stream:
1. it fails OStorageHelper::IsValidZipEntryFileName check, because
the file path contains ":\";
2. even if that were not the case, the required file can be absent
from user's system.

I suppose that intercepting the failure at the level of
OOXMLOLEHandler::attribute() is the best option, because at the
lower level it's unknown if this failure is fatal or not.

I suppose that it could be also useful to intercept specifically
failures in OStorageHelper::IsValidZipEntryFileName, checking if
the file exist externally, and asking users if they want to update
external links (as MSO does). Possibly it should be discussed
with UX team if that should be done, and if so, do it in separate
commit.

Change-Id: I240a6f69abe236eb790bb406c79f3b761fb4638a
Reviewed-on: https://gerrit.libreoffice.org/19963Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Andras Timar <andras.timar@collabora.com>

Change-Id: Iec71ad4918cd333f0a44d372017ecee300e3aca9
Reviewed-on: https://gerrit.libreoffice.org/20748Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Martin Hosken <martin_hosken@sil.org>

I'm a bit worried that some of our random test failures are related to
trying to reuse the same temp file in different tests.

Change-Id: I0ca4ace088a96530e6a62d01f979fefe63822b22
Reviewed-on: https://gerrit.libreoffice.org/21090Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

Change-Id: Ic9d90bb7f652599b5a6ce303aa026b7e4e255324

Change-Id: I2cd8cdd541fd4095aea8abd2ea78b11e7df77440

Change-Id: I0e16305cac5cd5e4824a4e2bab7e4ac10d2bd469

Change-Id: Id17aa3eea4d6ccb956f9c0b1fd97007ef0257955

I currently assume that this is responsible for some of our heisenbugs
on windows. I think the windows file locking is causing issues when two
test try to access the same file in parallel. This is more likely to
happen on the fast windows ci boxes.

Change-Id: I423f6c723c2ec558026867a118972e98279bd2c2

Duplicate <include layout="@layout/toolbar"/> statement found.
Problem could be caused by either
1) a differing xml reading mechanism across android versions
2) toolbar being accessed in a different way across android versions

Duplicate element removed, and linearlayout shifted below first toolbar.

Change-Id: I084b6498745bc72988f3a8eed12f7a72d261e267
Reviewed-on: https://gerrit.libreoffice.org/20422Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: jan iversen <jani@documentfoundation.org>

Change-Id: I451a7a04fd1578d3095e5931f0792a32870a647e

Change-Id: I08430479a2c8d1fd6e3fc357ba3069b3a7bb6ac8

Change-Id: I45c0b74c9d54120bfac85f16a336ac7ff487ed73

Change-Id: Iedeb2b87da0f230961c1c22275f980acbe7a9e5b

Fixed:
- TCP port got lost/reset when editing a server;
- in Gtk widget disabled comma;
- secure protocol checkbox always unchecked when editing a
  server.

Change-Id: I358fc7375552b29e4840a3616e4e47b95b88ed2c
Reviewed-on: https://gerrit.libreoffice.org/21039Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
Tested-by: Jan-Marek Glogowski <glogow@fbihome.de>

Slight misinterpretation of the
{Sunday, Monday, Monday, Tuesday, ..., Sunday}
sequence defined in ODFF.

Change-Id: I09ac711adf8a52db1c9efbb1c67dc908b8e06618

The filters map between a common subset of Word smart tags and Writer
RDF annotations, and when doing so, they need to know what path to use
for a smart tag namespace and also the other way around: what RDF types
are interesting for smart tag purposes.

It turns out there is BAILS specification at
<http://www.tscp.org/wp-content/uploads/2013/08/TSCP_BAILSv1.pdf> that
describes how to refer to BAF objects, so use that instead of our custom
RDF statement / document metadata key names.

Change-Id: Iac569608b05aa61547f664f2a5df7d46fe46da76

Change-Id: I342e9b5355c3ea09eede6c47b0f209f538ee82cb

Change-Id: Ic586d44d2ff0f913f655b8a7539326a6dea78477

Change-Id: I9db63e6c6b4df33387b9b4d59450494e8bd856f1

... which now has exactly 1 parameter; removed the now non-matching
required flag of a not existing second parameter. Luckily the resource
manager treats this as a separate record block and this 0 didn't harm
the subsequent 0, accidentally..

Change-Id: I0994ed75643245c1bdebc9a92ade77abdd1c61d8

Change-Id: I64b22f91bf56497b9f705e4773e24c5ba88a14ae

Change-Id: Id56e219782d7f858cdeb26232c7aabd4f643c9d9
Reviewed-on: https://gerrit.libreoffice.org/21020Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

...that had inadvertently been removed as part of a larger code removal in
6948c546 "tdf#75637: Resolve help images via a
vnd.libreoffice.image UCP"

Change-Id: Ic2d5e1a5fa5a10b240bb9e511e6dcb8097e58081

Change-Id: Ibc51fb4cc72163fb643a85ad3f0b6061b7d77ccc

Change-Id: Ib6676f6f940ce497ac6fe28189e1c3a4ed4ec0bf
Reviewed-on: https://gerrit.libreoffice.org/21032Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>

Change-Id: I77f49f09ce9fe5897f78044c0522210978c904d1

...that happen to be requested concurrently from multiple threads

Change-Id: Icecfb0b8d88c9123064689643eddf90a99d3b1b8

...instead of dereferencing null pointers

Change-Id: I9d1709468a5b601b9f3d86dadea7a8e817f449d8

...except when checking for infinity

Change-Id: If6e3b8965169cc615fa5d76422e1925866714936

Change-Id: I5ecd63d79e8be77879d3789c45079929696abe03

Change-Id: Ib45af8a56ac3adc428c530908cf1bbd95e9cc64c
Reviewed-on: https://gerrit.libreoffice.org/21065Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: jan iversen <jani@documentfoundation.org>

Avoid hundreds of presumably pointless warning messages in some unit
tests at least. The code explicitly checks and handles the asserted
condition not being true right after the DBG_ASSERTs.

Change-Id: I5482c56aeeadb8f85dfdd03e12960abd7e769c56

Change-Id: Ie24194fe04dafbc447cf8a8a015316e9ba6e9ac9
Reviewed-on: https://gerrit.libreoffice.org/21071Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Jenkins <ci@libreoffice.org>

Change-Id: I37948ff77d060dc18a583389966b52c06a95bdaf

"yeah, makes sense to remove it", says Stephan.

Change-Id: Ife7baa5814a856dca7f0f02ac3cb2521e2980851

Project: dictionaries  ce7755c7d3179d682dfaccace9e64b6a008c77d2

tdf#96782 updated German dictionaries

Change-Id: Ifa7aed93eaa0448ba530cc029ee55480060e1be5