Change-Id: Ic749119931db569bf26c8d8a58da7d468811f927
Reviewed-on: https://gerrit.libreoffice.org/10598Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I2b8662ec85b8f710aa17a2c6f59c4b35af7685f3

Change-Id: I5986efd3d5690cb63ea44afaba7705c6f747e7f8

Also, removed the unused hrc/src files.

Change-Id: Ice45dde1af7492e40e0847ead06bb26f4e58ed9c
Reviewed-on: https://gerrit.libreoffice.org/10595Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>

Change-Id: I2f3bb2e85457356a0e1ca313f3988eec40f362e7

Change-Id: I5d14fc4bd051c37802c0689d55d8557e26312a5d
Reviewed-on: https://gerrit.libreoffice.org/10606Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>

Change-Id: If2749e604d0375fa0af0eac9244c533e177f09ab
Reviewed-on: https://gerrit.libreoffice.org/10599Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>

Change-Id: Ie61d007857a62facac9d4e21ec494195041eeffb

since none of the call sites specify it

Change-Id: I9c15f0e042e21f6f78560c1962a533112d588c90

Regression from commit a5f9fb72 (fdo#80800 :
DOCX: Preservation of Direct Formatting for non first Table Cells,
2014-07-11), CT_Spacing's two attributes (line and lineRule) may come in
different order; but the change only handled the case when lineRule is
followed by line, and not the other way around.

This fixes a unit test failure in CppunitTest_sw_ooxmlexport's
testSpacingLineRule.

Change-Id: I892d97a97390228a59a129f096be39ce93b822d6

since all two of the actual call-sites only care about whether
it is a valid presentation or not, not what kind of presentation it is.

Change-Id: I75717c88878d37b2897741b0c833ff283b3fee59

Change-Id: Ic0e67b3e78fe6f38e8a255981c9aa9cfd939fd4b

Change-Id: Ibc64a17dc4a779e05946dfe5d1d12109e643a7fd

Change-Id: I0ee5f4f709aa521d85974ebb6518d8f2bce3f513

Change-Id: I719557813180c3f862ef4b00e24142fdbbb0daf0

Change-Id: I00804b2dd63df44478a14a3eaf2fdcd4e4ce5d09

(Seems you need a clean build to notice this...)

It looks like the cleanest method of getting lok_init into
a LibreOfficeKitInit.h header (in a c89 compatible way) is to
have it as a static function.

(inline is only available in C99 or later -- this is actually
 available on Linux which is the only place that we can actually
 use lok_init anyways currently, however given we have to keep
 c89 for the C code (for MSVC) compatibility, selectively enabling
 c99 would likely be more messy.)

Change-Id: I0493e7a68ed5397479220bb6ba8c3db870b6dd32

Update it to handle formula groups correctly.

Change-Id: I009a7fcf3d3fb17ef6951c50534ca6bc1fffc259

Change-Id: I46ccf0954f9397779244132488d93f3162cf04d6

so that it could be usable from unit test.

Change-Id: Iea10cb473bc17d7e030c018fd2c84fbeccce3e47

Easier than trying to figure out how to make the VC2010 project work
with VS2013, it seems. Luckily it works fine tojust have VS2013
upgrade the old project file and then pass that to msbuild.

Change-Id: I94c0248211767d97f2898f35b1b677aee372a329

Easier than trying to figure out how to make the VC2010 projec work
with VS2013, it seems. We only need a project file for the lcms2_DLL
project.

Change-Id: Icab47ac7625b9a492942ea0835fe52ef06cdf2d9

Change-Id: I030137cb379de04968fb144516e90dbd1bdd97f6

This avoids an ugly "Character" box in the dialog with a null byte in it.

Change-Id: Iee35a8e1bd6b57fb4eb8ae06722bd79ee1d5d8de

For RTF, the tab stops that are set directly on the paragraph are the
tab stops the paragraph has effectively; there is no equivalent of OOXML
<w:tab w:val="clear" w:pos="4536"/> that would override a tab stop of
the applied style; that is done by simply omitting the tab stop.

It would perhaps be possible to implement something to synthesize a
NS_ooxml::LN_Value_ST_TabJc_clear in the RTF tokenizer for this case,
but it's simpler to just generally disable domain mapper's
InitTabStopFromStyle() for RTF.

Change-Id: I7b0581be8db19ffda81c8d1da290abf0a0f69529

Change-Id: Ib25ae32be6132a9209eaa81db18b0659b73d5b82

Change-Id: I340ef55dc9a09bd196469ed51848b22ba986de8c

Change-Id: I97b1d03410e98c5ff2ad3cc15cef692e9b994a6c

Regression from ee9f23bb (docx export:
invalid sectPr added at the beginning of the doc, 2013-01-10), the
problem was that we even tried to generate section breaks at places
where the two page styles are in practice the same.

Change-Id: Iccf91ce542d9b075b93da25bcd42236db667e3d4

Change-Id: I24e7934002ebdde208db74ae3308b26875a3155b

There seems to be a maximum size that gdk's pixbuf
can handle, however I have been unable to find any
documentatation. Seeing as the current implementation
isn't realistically useable anyway, we might as well
set a hard limit here (in practice we'd have much smaller
tiles + compositing).

Specifically extras/source/shellnew/soffice.ods will fail
without this patch.

Change-Id: I6ac495adca8e15878989375ef8b2de472788279a

Change-Id: Iea5105cc33b436e9c0728df799b1ceb63f20e46e
Reviewed-on: https://gerrit.libreoffice.org/10579Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>

Looks like unintentional change made in
c4a593b6

Change-Id: If314a3f290c79909e3a807f9c9c95791c26067e9

The test document was converted from doc to docx using MS Word 2010.

Several fixes were required to make this test pass:

- Do not clear the "FirstIsShared" property on page styles, as the code
  instead uses the old fashioned method of translating a Word section
  with "different first page header/footer": two page styles linked
  together, the first page style and the follow page style.
  (Also remove a wrong test case which checks the FirstIsShared property)

- Do not clear the "HeaderIsShared"/"FooterIsShared" properties on the
  first page style, only on the follow page style.

- Actually set the "FollowStyle" property on the first page style to
  link it to the follow page style.  This didn't matter for the very
  first Word section because it was mapped to the default page styles
  "First Page" and "Standard" which are already linked, but it does
  matter for subsequent Word sections.

- For some reason setting a new page style at a section break was
  excluded in the case where the following section had a title page.
  Remove this exclusion.

- The exclusion mentioned in the last point was masking that bnc#751077
  was not entirely fixed.  To resolve that issue:
  When checking if the last paragraph of the section is empty, consider
  not just text content but also shapes.

- Remove a workaround for bnc#780843 involving copying of headers and
  footers from the "Standard" (first section) page style in the case
  where the following section had a title page.  This workaround is no
  longer needed as the test case passes without it.

Change-Id: Iacc9bba0720c11414da3e852892cff301ebbc4fe

Change-Id: Ia15e5a376b2a7503f56f183a555e21d1122fe66f

Change-Id: I22481191d5cbc905a9af7530e075acda21fcbeba

Change-Id: I62914ab65258de36790387b7a8865a32b0d7bca6
Reviewed-on: https://gerrit.libreoffice.org/10587Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>

Change-Id: Id9fbffbf74d7583bf1ac8239899abdf0c2347cf2
Reviewed-on: https://gerrit.libreoffice.org/10573Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>