libreoffice

Files

Miklos Vajna 9781a8786d tdf#89698 DOCX import: inline picture should have no spacing

Commit 3d7e168a2a (n#783638 DOCX import of
wp:inline's distT/B/L/R attributes, 2012-10-11) was about a picture that
had non-zero spacing in LO, but zero in Word. The hope was that the
problem is just that the value is not imported.

Then commit a88ac70840 (fdo#63685
wp:inline's distT/B/L/R is in EMU's, not twips, 2013-04-19) was about a
picture that had so large spacing that the picture become invisible.
Fixing the unit of the spacing value made the picture visible again.

What was missed is that this value is just stored in the doc model, but
layout in Word doesn't use it at all till the anchoring is as-char.
Given that in LO as-char anchoring supports real spacing, just don't
import these values to have the same layout. That's what the WW8 import
does, too.

Change-Id: I1244269e06c5d190e8340349ddc12ae7b0572a4d

2015-06-24 09:16:38 +02:00

complex

java: 'final static' to 'static final'

2015-06-15 08:45:19 +00:00

core

cppcheck:redundantAssignment

2015-06-15 13:34:14 +02:00

extras

tdf#89698 DOCX import: inline picture should have no spacing

2015-06-24 09:16:38 +02:00

python

test inserting/remove writer table rows/cols

2015-06-22 20:41:23 +02:00

tiledrendering

cppcheck: noExplicitConstructor

2015-05-27 13:54:54 +01:00

unoapi

split sw unoapi test for performance

2015-05-29 11:51:56 +00:00

README

…

README

You can find different types of Writer tests here, the following directories
are available:

- core:
  - filters-test: loads different file types (see SwFiltersTest::testCVEs() for
    the list of supported filter types), and only makes sure Writer does not
    crash. To add new tests, you just need to drop in the test files to the
    relevant directory, no code change is necessary.
  - uwriter: this test has access to private Writer symbols, add new tests here
    if you need that.
- extras:
  - see its own README -- executes import and export filters and asserts the
    UNO model to verify the resulting document is the expected one.
  - also, any new C++ test that links to libsw (but does not need access to
    private Writer symbols) should go in this directory, whether using the UNO
    API or the internal one.
- complex: JUnit-based tests using the UNO API
- unoapi: JUnit-based test trying to get/set every UNO property, etc.