Change-Id: If37ef9f68711da3a0aa9a3ba59b111a8a23421df

DocxAttributeOutput is getting huge, and the drawing-related
functionality is an obvious subset the can be separated from the rest of
the calls. Move most of that into the new DocxSdrExport.

Change-Id: I6e5c750e2bef07730c97fd018f042883721ac410

Change-Id: Ie8a1ce8628fa0f31ae6d6a3f1303342c145e33aa

Change-Id: I6b3f9316c3eb907912aeff1715705a95bbbf547c

Change-Id: I05c5eaf4575dc4b8c8d4e3c45d644a51aab84f0a

Change-Id: I7f5d31c3b3e128b2df4d83c915673bf7b5d2ab8c

dd0990db "fdo#72463 RowSet: on execute when not
dirty, rebuild cache" had temporarily introduced a bug that caused m_pParseTree
to be null here during JunitTest_dbaccess_unoapi, but Lionel states that it
cannot legitimately be null, even though the computation of m_bIsCount in the
ctor takes potentially null m_pParseTree into account.

Change-Id: If95f076a4c80f80cd58bba83521633fe8bb71f5d

To avoid the impression that this reference box takes a range...

Change-Id: I3a69cf496f013779692c17fb943dcc34a1692275

...it was never meant to be called by client code anyway and is no longer needed
to be exposed since the global service manager implementation moved to
cppuhelper.

Change-Id: If2d0510b2364084d36edeb156a3459d9b8aeb983

Change-Id: I4ed800ad17750c87788108417c8a7b1817853115

code has no function, except that calc documents with formula
ZELLERROR will not produce an error. But the formula is not
interpreted, so remains 'dead code'.

Change-Id: I6e7df7040a0273bcd3ebd497055924b7afdd3311
Reviewed-on: https://gerrit.libreoffice.org/7018Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Unfortunately this patch creates a very weird ( and took me forever to find
) bug ( fdo#60805 ). Basically certain double line borders seems to
dissappear at certain zoom levels. I guess maybe its possible to tweak
the create2DDecomposition to process the line as hairline at those problematic
zoom levels ( but I suspect that actually would look worse ) Best maybe
would be to tweak the rendering/painting ( but isn't that processor specific
maybe ? ) as is maybe this problem. I admit this is outside my comfort zone :/

This reverts commit a551cad4.

Change-Id: Idb25493ffb038cb1f8ae9b364a29052abafd940d

Change-Id: I79fa15d539bcb86610dd4def08536c33bd2a10c2

That is the only choice that makes sense, since the
(Prepared)Statement could die (go out of scope) before the ResultSet.
User code could do that, if it does not "need" the (Prepared)Statement
anymore. Also, it is only natural for user code to dispose a ResultSet
that it does not need anymore.

So we need to create a fresh ResultSet each time.

The "luck" here is that the sdbc file driver does not implement
the XMultipleResults interface; things get more hairy then.

Change-Id: Ibf2cb5e5b7ca90432a289c185a6b4fe32d1ba565

    1] Libreoffice gets crashed while saving.

    2] This caused:
        "testCrashWhileSave.docx" file crashes on save
         Tested on Libreoffice 4.2

    Implementation:
    1] It crashes when we are trying to access cell number 2 from
       cells vector which contains only single cell. So put check
       for cell number which we are accessing and Number of cells
       in single row.
    2] As we are exporting Header and footer in between when we are
       exporting document.xml. In this case we are facing issue in
       table export for header and footer. Because flags for table
       is getting shared in both export.
       So we are switching between flags in between exporting
       "document.xml" and Header & footer
       export.

    After fix:
    1] No crash on save for "testCrashWhileSave.docx" and
       opens successfully on MS Office 2010
       Added Unit test case in export.

Conflicts:
	sw/qa/extras/ooxmlexport/ooxmlexport.cxx
Reviewed on:
	https://gerrit.libreoffice.org/6676

Change-Id: Iefbf565f7b512d76ac68e9353e225edca425ef06

Change-Id: I5a4f80e1f6b4cc834c921d4c4780989c90cbefe2

Change-Id: Ia8e071ebe00fb8c72973614077e778aef55fb1ab

Change-Id: I9beea6119dbb1c12ff053e5776f15d40a3389a8b

No point in connecting to eg. ftp to get a thumbnail ;-)

Change-Id: I017c59196c294242366f2254eeacd9056455c1bc

Change-Id: I62c0479414ab6748039498e1bc2b3bc9d7c4ef05

Change-Id: I8ae72249853a03b1dfca0ecd10eef47e9aa7cbfe

So that the frame around the picture is similar to the previews; otherwise
looks disturbing.

Change-Id: Ie7f973e15c29a34c0f368b5e0f5a152d5cead39f

Change-Id: If61aefc1d27d7bca2e8242b404db685a503bcf0e

Change-Id: I48fc6fa86a9953db87e59a83714d4d7b0ff8d64a

Change-Id: I91899493479eb60c955dac3891a38913ad871376

It is /org.openoffice.Office.Common/Security/EnableExpertConfiguration with
values true/false; defaults to true.

Change-Id: I5a18d16182c28a13169677b11f68884f34c11c63

Based on Mirek's suggestion; looks better.

Change-Id: I3468450ee4c8ba27cd26a40c7ed11f0b4df9c42d

Change-Id: I1ecd3b9c74fb973769036defba96d73c5995175f

Change-Id: Ic498e5703ab48719f998be6da3f245843cc0979d
Reviewed-on: https://gerrit.libreoffice.org/6849Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: I44415f976a47bf676ab8c2f309590eb2c8afb6ce

Problem Description: While saving the file LO shows the error
"This file could not be save".
The root cause was memory leak.

Conflicts:
	sw/qa/extras/ooxmlexport/ooxmlexport.cxx
Reviewed on:
	https://gerrit.libreoffice.org/6850

Change-Id: Iacc185780c14760056a7d690eb113d4dde1de034

Change-Id: Id9b3d81482104e9e78b986c9a78704b01cd0fba2

Change-Id: I5fcac443a0b243814a8e5d3075ed4b484e977bec

Change-Id: I7d6facb76317d8e7de3adbafdf3763f37c1b0837

Either missing braces around the else branch, or inconsistent indentation. I
guessed it was the former and added braces.

Change-Id: Ic5e7db892774d48ba6db09a40741e5fbbdc95994

   1. Glosary folder is imported as Intrograb and exported.
   2. Added unit test case

Reviewed on:
	https://gerrit.libreoffice.org/6825

Conflicts:
	sw/qa/extras/ooxmlexport/ooxmlexport.cxx
	writerfilter/source/filter/ImportFilter.cxx

Change-Id: Ifd51a75a65e030d44d30e02cd7ab51fb088186b3

(cherry picked from commit 6f53c4f2)

Change-Id: I76e21409fee4f39bd6f048636e4fbc392807a486

Change-Id: I8beaf1f4a1ea685af22ae0dafbff767bee98d3b4

    - File was giving corruption message if saved in LO.
    - Issue due to video file.
    - Attached file contain .mov which was not handled properly.
    - Added mov extension support in graphic filter.

Reviewed on:
	https://gerrit.libreoffice.org/6818

Change-Id: Ia278127ddc4afcd2d5fe04e86ed6201fb28dc04f

Change-Id: Ic6fbb345e333d67f967a3ea09a5a90ecef910040