Change-Id: I05aa9a5ad5d97a1ead3d30298f45e7aeb62d0652

Change-Id: Ifd98e11380bf00f6126e4c81bcd0cbaf5b22f70d

Change-Id: I2ea94a510fd79f6fe3dcc5021d142b7b5f99f67f

When two pictures apply different effects to the same picture, it is
only saved once in the original document. Added a cache to DrawingML
to know if the picture has already been exported, and added a test
for it.

Change-Id: Ia25f3d8f2f46d61f18aefc22fdfdbcdc72f2d916

When Word applies an artistic effect, it creates two embedded files;
one contains the bitmap with the effect and the other one contains the
original bitmap to be able to undo the effect.

This patch reads the original bitmap, stores it in the shape grab bag
and saves it back to the docx file. Added unit tests too.

TODO: right now, if two effects point to the same original bitmap it
is stored twice, we should improve this.

Change-Id: Ia72034a257739abe4ffafa0f42b2a912e4bf9436

Bitmaps can define artistic effects like in the following example:

  <a:blip r:embed="rId5">
    <a:extLst>
      <a:ext uri="{BEBA8EAE-BF5A-486C-A8C5-ECC9F3942E4B}">
        <a14:imgProps
         xmlns:a14="http://schemas.microsoft.com/office/drawing/2010/main">
          <a14:imgLayer r:embed="rId6">
            <a14:imgEffect>
              <a14:artisticMarker trans="14000" size="80" />
            </a14:imgEffect>
          </a14:imgLayer>
        </a14:imgProps>
      </a:ext>
    </a:extLst>
  </a:blip>

LO core doesn't support them, but I'm preserving them using the shape
grab bag. Bitmaps must not be transformed to a SwXTextGraphicObject
so the grab bag of the XShape is not discarded.

Added several Context and Properties objects on the import side to
traverse and save the relevant tags, and added the corresponding code
on the export side to extract the grab bag and output the effect back.

Also added a unit test for a selection of artistic effects.

TODO: Word saves the original bitmap as an embedded wdp file so the
effect can be undone. We must preserve it too and add the reference to
the a14:imgLayer tag.

Change-Id: I61d427f83e4c8f353eb073da0114cd73ba50ba4b

Added the artistic effects defined in the MS-ODRAWXML extension. Ref:
http://msdn.microsoft.com/en-us/library/dd905216(v=office.12).aspx

Change-Id: I24c5e5bbe569f160d300a7a7293ca047cb7a1b88.

Change-Id: I53662b9d48ae44c21c9cc79bda01487d87e8dfdd

Change-Id: I8d9663f8dedda8e7006e7ac6545cb15188a1ec2d

Change-Id: Ic000d3a3920dddb8cc8585bb31127d14cfc35eb7

Change-Id: I844561cc6f858b6aed55caaf0d92529486cb486e

Change-Id: I22cd98a35c6c638e3476d54b742762d8a2dfa7fa

and hopefully a gadzillion more, but I've said that before :-(

Change-Id: I2e36485ae2ce831fdf250464b254d42f5bc55fe3

Change-Id: I568ba1a942acd622611fb53210e303147b77601f

Change-Id: I833b8b9532c61f666755ed5e92135da3aeb55f27

Change-Id: I765dd9bab26e3736c6b18a291cfd108342644e8e

Change-Id: I2eb374a9209cf4bbf9e2b533ec2522bc1efe6468

Change-Id: Ie82c16d7d7b3f4fed09bed1d6adec32d5d3934e5

Change-Id: I2f866aa16704bc5492e0e0b78136fdfe41caa7a5

Signed-off-by: Stephan Bergmann <sbergman@redhat.com>; plus some cosmetics to
silence loplugin:bodynotinblock.

Change-Id: I8ff9da84021635c9de66c9544b46834a2d9efcf7

Groupshape text is provided by editeng, redlining is available in Writer
text only. But still, instead of ignoring both deletions and insertions
in group shape text, we could at least show the latest version
correctly, i.e. ignore deletions but import insertions.

Change-Id: I12df2ca1a8d27f9496a8036e521f8820d7075053

Change-Id: Ia1614759558e73686fce137eb52fb623eae4a4e5

Change-Id: Iba7bb88139a97e919739363cd85f3e822062b694

Change-Id: Iff0692768cbcaa68f79404a9a933044fe8bb9096

Change-Id: I198fb0193fed891c4dd8a8a92c29e36f6c4d48b9

	Issue :
	- Document contains a Section break(Next Page) with a drawing.
	- Section break is manullay adjusted before the drawing.
	  Hence in original document.xml it wsectPr comes as
	  a part of w:pPr of paragraph.
	- But in RT in document.xml, section break is written
	  by adding a dummy paragraph.
	- This is because <w:drawing> also contains a paragraph
	  and hence when encounters section property LO creates
	  a dummy paragraph and writes it in between runs.
	- This was causing the corruption.

	Implementation :
	- Added a member varaible m_bDMLAndVMLDrawingOpen.
	- It is set to true when it writes drawing.
	- It's value is checked in DocxAttributeOutput::EndParagraph()
	  If m_bDMLAndVMLDrawingOpen is true Do Not make
	  m_bParagraphOpened to false, as one more paragraph is still
	  open.
	- This will postpone the writing od Section property and will
	  be written inside w:pPr and no dummy paragraph will get
	  created.
	- Added Export Unit test case.

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

... as they can be disabled and thus are not there at install

Change-Id: I197b5053971d2721114b2ebc7b3c31db36c3f58e

We need to wait until all the affected cells get marked dirty at the
end of the deletion process.

Change-Id: I49618fcc386ec2209f5f0267d50257ecb8dd21d1

Change-Id: If8ed8b74b58efd948772376a14172b52ff588f82

Change-Id: I10bdfc3356bda66fefa59fa2c9f63f9231d8728e

Change-Id: I2447498cf92da91a7fb2d67ee041d603ae16fe25

Change-Id: I82a517a267cceaac4dd1030d45c67fc070e22def

Change-Id: Id8adb7517960a33f9900cb773b62b84db71e795a

Change-Id: I010c7c194bf0680a499077b6b364498a09542764

Change-Id: Ib79f0c525608d279eebe820bfc82e84dd3518c29

Change-Id: I35adb022f12c6833f4f29b2e8dad44394a2c4be5

The chart object can be destroyed after the context.

Change-Id: I5ae370638f296ea314ee11680e0a8d81a8fdbe69

Change-Id: I5bdf6c3b313a73126cb692e5101836f424a2fc08

Change-Id: Ifb068efb553ed24a7caf65dbab28726bdeced0e6