| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The XDocuments representing the DOM of an OOXML's theme document is
now stored as the PropertyValue "OOXTheme" into the "InteropGraBag"
property of the SwXTextDocument.
Added the importSubStream() method to the
writerfilter::ooxml::OOXMLDocumentImpl class in order to create the
XDocument for the theme XML fragment stream and invoked it during the
resolve() method.
Modified the writerfilter::ooxml::OOXMLDocument abstract class to be
able to hold the OOXML's theme XDocument. Added the set/getTheme()
methods to store and obtain the XDocument directly.
Modified the WriterFilter::filter() method to store the OOXML's theme
XDocument in the "InteropGrabBag" property of the TextDocument service
SwXTextDocument implementation.
Updated the UTs accordingly.
Change-Id: I3960590fcf4856caf770908b983ffb6898f061c0
Reviewed-on: https://gerrit.libreoffice.org/6002
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Enabled parsing of chart in writer module.
2. While parsing chart is read as ole2shape. Then converted into TextEmbedded object for chart.
3. While exporting postponed chart writing after rpr tag.
4. Generated unique id for each chart.
5. Corrected content type of chart in export.
Change-Id: I6a1ca0c34e03e17cc3dd8a183580132ea7af5c48
Reviewed-on: https://gerrit.libreoffice.org/5976
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
|
|
|
|
|
|
| |
Compare styleId against styleId, not style name against styleId.
Change-Id: I42bbb8a04424780772065585cc8ff56d906a48e4
|
|
|
|
| |
Change-Id: Iacb9b09f237ddab3d68f4993014efb3b4793b8e7
|
|
|
|
|
|
| |
Wow, has been broken like this since 2007...
Change-Id: I32a84e1444ed6fd89161f2060a35296044516863
|
|
|
|
|
|
| |
[And kill one unhelpful one - comments a removal of something.]
Change-Id: Ia4229fe889aa0aae115e6ab9b6808e0f054bb199
|
|
|
|
| |
Change-Id: I7c44a2bdb69563953d3257b435aeed5bae50f7b2
|
|
|
|
|
|
|
| |
Change-Id: Icaa0560b812b96e41c52d7a43267873fe364ceb7
Reviewed-on: https://gerrit.libreoffice.org/5904
Reviewed-by: Andrzej J.R. Hunt <andrzej@ahunt.org>
Tested-by: Andrzej J.R. Hunt <andrzej@ahunt.org>
|
|
|
|
|
|
|
| |
Change-Id: I83619c47d435b9ee7bd0de3121832f84046a6d18
Reviewed-on: https://gerrit.libreoffice.org/5903
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
|
|
| |
Change-Id: I9bcf02b270200fd146d2bfee6f15ff1f9ad8888b
|
|
|
|
|
|
|
| |
In general, paste should not deal with page styles. In this case, it
even caused an additional page break.
Change-Id: Ia7c5a9ad844821b6622babfbd94469ec3c04cf0a
|
|
|
|
|
|
|
|
|
|
| |
-Use sprm:CBrc attribute for all MS filter (for ooxml too).
-Extract general code to FormatCharBorder() method, it selects
the border side and decides whether add shadow to the border.
-RTF export has a color table, which must be filled with border
colors before the actual export.temp
Change-Id: Ic3ceae6e19ddc2ed5aaa8de85617f9a592289b4f
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Modify HasTextItem() method to able to get
character attributes during export.
(in this case RES_CHARTR_SHADOW)
- Only one side of the border can be exported.
Selecting order: (top, left, bottom, right)
- During import set all four side and use the Word
default shadow type (back, bottom-right, border width wide)
Change-Id: I3e1e27a2ef2d77b397f2ca8efe578e09271bcf8c
|
|
|
|
| |
Change-Id: I6d5e8d3fd69189935a3338fee19b60022f70a7eb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were two problems here:
1) OOXML has no way to explicitly disable the footnote separator, what
is does is that it omits the <w:separator/> element in that case. We
didn't parse that previously -- now we do, and if it's missing, the
separator is disabled.
2) The footnote stream isn't read by the importer, only when the main
stream references the footnote one, the relevant part of it is parsed.
At the moment we always parse the first (special, "separator") entry in
the footnote stream, that may be optimized later if it becomes a
bottleneck.
Change-Id: Ie588270a212fc90fc41095029a362cfd832b24f8
|
|
|
|
|
|
|
|
|
|
| |
This is a port of commit 8fe8bd6c3b5b1a539b7370f8c457fa69c061d2de
"Related: fdo#61594 SwWW8ImplReader::StartApo: don't always start a
frame" from the WW8 filter to the DOCX one.
(regression from edc4861a68e0269b83b17e0ec57912a1ce4220ad)
Change-Id: If1bb4a8a3786aacd618585cf859b57ce9be85c51
|
|
|
|
| |
Change-Id: Ibb250148d41d1929fa17dd993bb71c93c0e09dcf
|
|
|
|
| |
Change-Id: I240b95e09d3555c0fdcdf6c4b9eb458ad82460e4
|
|
|
|
|
|
|
|
|
|
| |
Mainly the problem seems to be that Stein's GCD algorithm requires
non-negative input parameters, and the document has this:
<wp:lineTo x="-480" y="6104"/>
(regression from 86898639d4144a078ed295d0a8bef406868802cb)
Change-Id: I8da1272c3caae84f43472aa4acb65ed66dfbd8ae
|
|
|
|
| |
Change-Id: I9dce59ecd8a2d2bfadb8c7273cd46c6c0cf17774
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bugdoc has a table with a single cell, and also a nested table in
that cell. Both tables have auto width. The problem was that the width
of the outer table was too large.
There is a trick in DomainMapperTableManager::startLevel() to get the
cell widths at the correct level: do the same in
DomainMapperTableManager::endLevel(), and that'll fix the table width
problem. (Because with that, the outer table will correctly have access
to its cell width.)
Change-Id: Ib750f0475364fd7e47c445cb54f2df34f3af085d
|
|
|
|
|
|
|
|
|
| |
And do the same for w:after / w:afterAutospacing. The spec says that if
w:beforeAutospacing is read, w:before should be ignored, this implies
that if we already had w:beforeAutospacing, w:before should not
overwrite the already existing top margin.
Change-Id: I9437cb5c6fc352a360e27aa279d0a789706c5578
|
|
|
|
|
|
|
| |
Paragraph auto spacing (before and after) without the
w:doNotUseHTMLParagraphAutoSpacing compat option was incorrect.
Change-Id: I56d6153f7c489de7fceaf6fab7325c42ee8f9cae
|
|
|
|
| |
Change-Id: I2aed7907c79905158714dc1b26ae1aefc1fcccc6
|
|
|
|
|
|
|
| |
This was in writerfilter, but we'll need it soon in sw as well, so move
it down to msfilter.
Change-Id: I8efe02b6bbe8f391d9e14857ed58dbae184d5632
|
|
|
|
| |
Change-Id: I15e09017eccc3f0e5ed8cab9c3de3677c8a580fa
|
|
|
|
|
|
|
|
| |
Change-Id: If4940b17bcee0d06fa8dc9bf9faa708cf6d0db1c
Signed-off-by: Adam Co <rattles2013@gmail.com>
Reviewed-on: https://gerrit.libreoffice.org/5528
Reviewed-by: Miklos Vajna <vmiklos@suse.cz>
Tested-by: Miklos Vajna <vmiklos@suse.cz>
|
|
|
|
|
|
| |
Regression from 60c17b2873506ed8b068b34840aecda0c1d9bd65.
Change-Id: Ie16d611622e6a814d5cbea00c3f992cd9ecba027
|
|
|
|
| |
Change-Id: I82ef1072bfeb1195152ef7f1ea743653ac102b37
|
|
|
|
|
|
|
| |
Compiler plugin to replace with matching number(), boolean() or OUString ctor,
ran it, few manual tweaks, mark as really deprecated.
Change-Id: I4a79bdbcf4c460d21e73b635d2bd3725c22876b2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 4a507f732d82c188ad81b022cbe3037951e58ac3 added an exception to
RTF_PARD (reset paragraph properties) handling: when we're inside a
table, it should not reset the fact that we're inside a table (which is
a paragraph property).
However, instead of just re-adding that property, it disabled resetting
for all properties, and we had a growing list of exceptions since then.
The next thing to add there would be the paragraph attributes, which
contains the style information. Instead of growing that ad-hoc list,
reset everything again and just re-add the "in table" SPRM.
This makes the second and later paragraphs in the A1 cell of the bugdoc
have proper font size.
Change-Id: I2de80894fcd5da3bf45d221af9a04a307c70a29b
|
|
|
|
|
|
|
| |
The bugdoc does not have a styles.xml but a stylesWithEffects.xml,
whatever that may mean. (the app.xml contains "Microsoft Macintosh Word")
Change-Id: If3d11c5d166dcaf3d94129339559787c20e6db46
|
|
|
|
| |
Change-Id: I8d2485962947eac8acc9ada384a9c1bd4cb22503
|
|
|
|
| |
Change-Id: I5bc51b739c663d3e123c9d7fb4c2a70f01f8c841
|
|
|
|
|
|
|
|
|
|
|
| |
Left margin wasn't implemented, that's simple. Right margin of the table
was set to the cell margin in commit
53d27a30ce5f2c9f7d37a4089286116854c16215, which turns out to be wrong:
it's true that the right margin should be >0, but not because of the
cell margin but because of the table margin. The new behavior matches
what the binary import always did.
Change-Id: Ifc24e4f086c49d5d575defdfca1d27e497fa03dc
|
|
|
|
| |
Change-Id: Ia3a95d785d19f7be750e3723c1c159395ae8476f
|
|
|
|
| |
Change-Id: I5cbb44df09291b8a1b74e8aa176d6471960b3391
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Word, just like normal tables, floating tables should be positioned
in a way that the start of the cell text has the same horizontal
position as normal paragraph text.
To emulate this, first the table should be moved left by the table
border distance, then also by the border with / 2; as done for
non-floating tables already.
Change-Id: I581311fbb08009e6c1839106e8f615d078a4a705
|
|
|
|
|
|
|
|
|
| |
m_nMaxFixedWidth wasn't reset across tables, so the counted width for
the first table in the bugdoc affected the second as well.
Regression from 74c5ed19f430327988194cdcd6bdff09591a93fa.
Change-Id: I69a5fa402f2e0170a1ea0269fd73e4ad8f7fede1
|
|
|
|
|
|
| |
Otherwise global w:spacing will be used even if overriden locally.
Change-Id: I01f0a3a323566f6e29faf73bf9d2ba874565eb42
|
|
|
|
| |
Change-Id: I566c491d65b65def65b78afb583624d8272027e0
|
|
|
|
| |
Change-Id: I7892224a118b6566e26b3ffc472c88f3c7f58620
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were multiple problems here:
- xFoo->createTextCursorByRange() got a text range argument,
where the text range wasn't from the xFoo text
- it was assumed that all XText implements text::XParagraphCursor as
well, but this is not true for e.g. comment text
- commented text ranges were pasted as normal comments (once again, the
insert position wasn't passed around)
Change-Id: I9a975a08b08a7f32b1ee71e42f58736cc0dbb09d
|
|
|
|
| |
Change-Id: Ifbf7db8044ee28f5f24c03480391a315358a2db4
|
|
|
|
|
|
|
|
| |
It was a customshape, but Word seems to handle the shape as a rectangle
when shapeType is missing. This makes the text in the textboxes of the
bugdoc wrap properly.
Change-Id: I56e044f42ead348bbb79addc36fa13c82a7ffc29
|
|
|
|
|
|
|
|
|
|
|
| |
The real change is in RTFSdrImport::applyProperty(), the rest is just
refactoring to be able to read the "is textframe" property from that
method.
With this, the transparent big rectangle in the bugdoc no longer hides
the text on the first page.
Change-Id: I04cca3ade93a63edf608df047bef3bdccf8d3605
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The document itself is stupid and uses a SURROUND_THROUGH object with a number
of empty lines that make it act is if it in fact was SURROUND_NONE, rather
than actually disabling wrapping for the object and be done with it.
But the difference was that Word still managed to fit those empty lines
next to the object into the little space that was there, while LO already
considered the space too small. So keep a compatibility setting for Word
documents in order to avoid problems with such lame documents and hopefully
that's enough.
Change-Id: I7d17b90de381fd86914ce5efd9c5a29fe4850edc
|
|
|
|
|
|
| |
Previously this was only handled for drawinglayer shapes.
Change-Id: I7ce440a27ebe44fc867b8a7f4ee62217076677f0
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The document had 3 sections, separated by continuous section breaks.
Previously only margins from the last section were imported, this way
the first page had default margins.
Now margins are also applied when we hit continuous section breaks. This
way margin values from the last section break affecting the page wins. A
later commit could improve this further by setting the minimum of these
and setting a section margin for each non-minimal sections.
Change-Id: I4d9a4585e795220533909bd1d467d933caaa0d71
|
|
|
|
| |
Change-Id: If1bd91f28a96bd0eb53e4057e51db900f8b2c52b
|