Age | Commit message (Collapse) | Author |
|
Change-Id: Ie9f9c5cc94b87914bcd7d5392f6fd1ee447e94ec
|
|
Change-Id: I9b273543ccf2eaa87116c6e1475860e9e872c445
|
|
Change-Id: Ia4fb0b489509364c641f8e1e695353bbdb036b59
|
|
... that was causing test failures on some but not all platforms.
Change-Id: I0d04cd6e540ea2693a3ec8511d615a9b0fecf456
|
|
Change-Id: Ic2479771129dbb0284292bf8712179567f516b0e
|
|
Change-Id: I546b96a5628d2ad186b5b626cce28f67841db157
|
|
Remark test document not moved, due to other test cases.
Change-Id: I9564b72fae60cceb60121fec06e1ed015add8453
Reviewed-on: https://gerrit.libreoffice.org/20703
Reviewed-by: jan iversen <jani@documentfoundation.org>
Tested-by: jan iversen <jani@documentfoundation.org>
|
|
Turns out that SfxObjectShell::CreateShellID() will produce the
SfxMedium's base URL if it exists, so
EmbeddedObjectContainer::CopyAndGetEmbeddedObject() already has
parameters, sw just needs to set them.
Change-Id: I36cedfde4e7c2e25c43c66a30d8ca572f099ad69
|
|
... mainly for the (unlikely) case of ODF embedded objects in MSO binary
files, which can be created by toggling the
Tools->Options->Load/Save->Microsoft Office export settings.
Change-Id: I270f1516b70b20ec0b60cfbd17c2c327c3d9efd0
|
|
When the object is edited in the UI, the m_xClient is set to a
SfxInPlaceClient and the DocumentBaseURL is retrieved from it. But if
the object is not edited, it will be loaded during export via the API
and without a m_xClient; in this case the DocumentBaseURL must have been
set previously to be available during import.
There appears to be no way to get the URL of the document via the API
while it is being imported; SfxBaseModel's m_sURL is unfortunately only
initialized from SfxObjectShell::FinishedLoading().
During ODF import, the SvXMLEmbeddedObjectHelper creates the
embedded object, so let's make it pass in the parent's BaseURL.
The "DefaultParentBaseURL" parameter already exists but was unused
previously.
Change-Id: I3d1ed29b3a2c0e77ec606a1d09f7bc07e7860733
|
|
Change-Id: I272afd26addfde5065939db4a04c2f0f01aa28c8
|
|
If the user edits an embedded object it is converted to ODF, so we
really need to be able to store such objects.
Ensure that the proper MediaType is set in [Content_Types].xml,
the package relationship type in document.xml.rels and
the proper ProgID attribute in document.xml.
Change-Id: I3c78c5ab5b4d534213af5e773fe0c6c2c92d9104
|
|
Change-Id: Iebb4ac4a7307bb8482ca735096503da03448fee7
|
|
Change-Id: Ieb308d717aa661fa51bd1b9dd3d0a12ca61337c1
|
|
Revert "Fix tdf#77514 CJK ruby text in RTL( vertical ) base line issue."
This reverts commit b14861e1dfb9f83d26d6032ae96b664845528f2a.
Conflicts:
sw/source/core/text/itrpaint.cxx
Change-Id: I4b7f7437014032566227f745e5e81b6a01ba022f
Reviewed-on: https://gerrit.libreoffice.org/20358
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
it always paint partial table border which have line style of DOUBLE_THIN.
Becouse the partial of the border line is out of the invalid window rect.
so, we extend it.
Change-Id: I9d95ca71a96cfa869c68d9d2200f29c7cd447eca
Reviewed-on: https://gerrit.libreoffice.org/20701
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: jan iversen <jani@documentfoundation.org>
|
|
The situation is similar to commit
79fb61efb847405fa47235002b52ee8efad5e339 (tdf#92379: svx: don't
overwrite fo:background-color on ODF import, 2015-08-21), except that
here text frames had the problem of loosing colors when transparency is
set.
Fix the problem by informing getSvxBrushItemFromSourceSet() about if
we're in XML import or not.
Change-Id: Id1adf60b14a3762f0a2a43c49caeed9f6ea039be
|
|
Change-Id: I50e3772b7b479d2cf1eb644c7334d0f987874ccb
|
|
Change-Id: I8f9e74f7fbbff055c67cafba5d534db4635e5399
|
|
No testcase as our importer doesn't read this structure, but Word
complained about this.
Change-Id: I91f947233802ea6fb103c32fd774bad09c56764e
|
|
And also relax two import conditions, as it turns out Word accept those.
So instead of checking for each offset/length one by one, only check
once.
It's now as good as the DOCX one, I believe.
Change-Id: I1890ef61fdbbd2ab6facaf3e787f75b791adcfdc
|
|
this will make it easier to implement native help tips
Change-Id: I984dfadaf02e9b7bf542ba82cf070911c89cb699
|
|
Change-Id: Icef8c521d6a0ad1ee1fa1eadf2e472910c9193f2
|
|
Change-Id: I1d1f8aa28438209fbe3258b4b4418fcdfaabf78c
|
|
Change-Id: I05eda6067308119a388238eed356531851000691
|
|
Change-Id: I30ba25e035fae08c06b17e2bafcb8a1147d4e12d
|
|
This contains the name of the bookmarks, except that factoid bookmarks
don't really have names...
Change-Id: I0fe3b983edf206d51e4d1cf4a66919fce0167738
|
|
Change-Id: Ibefc4b908c752a6256b168b4045afb400ba8b17a
|
|
An .odt table can “keep with next paragraph”. This means that the entire
table may shift to the next page and all the rows will keep together as
the table attempts to stay on the same page as the following paragraph.
There is no “keep with next” property for .doc tables, but each row CAN
be kept with the following one. When exporting an .odt file to .doc,
setting each row like this will keep the text flow similar to the
original .odt's layout.
This commit only hinders the table from splitting - it does not actually
affect keeping with the following paragraph.
This functionality already exists in the code, but was broken
by a variable that “changed meaning” almost as soon as the
functionality was introduced.
A followup commit will deal with "full page" situations when the kept
sections are too large to fit on a single page and so the table should
split instead of start a new page. The only situation that can't be
handled nicely is a single table kept-with-next that spans more than
one page. Such tables ought not be marked as keep-with-next anyway.
Change-Id: I401772b3fa2e329b7b0890e67639cbca8c845206
Reviewed-on: https://gerrit.libreoffice.org/20217
Reviewed-by: Justin Luth <justin_luth@sil.org>
Tested-by: Justin Luth <justin_luth@sil.org>
|
|
Change-Id: If490e8523dbedabdf4124b1bd1a5ba08678dc06e
|
|
Taking into consideration the changes from
https://gerrit.libreoffice.org/20446
Change-Id: If2419574611b890170e9d5eb69703e5c8c21c3c2
|
|
Change-Id: I8bf4557094bc32ad58760e822689c3f1d5f33c8f
|
|
Change-Id: I7a161afb520c3f26be0d5846a3ef2300c558a7d2
|
|
Change-Id: I5191a48d3cadc8b9e4c1cc5f4ea99adb0071002f
|
|
Previously the text was too long, ending on second page,
and table was on third page here, but is expected on second.
Change font to 'Liberation Serif' which seems to be used elsewhere,
and set line spacing to 'single' which makes the test succeed.
Change-Id: I4fc903c5d83308608e70e3e440d5277abd487052
|
|
adds detection of css::table::BorderLineStyle::NONE
to the LineListBox and stops painting NONE style lines
Change-Id: Ib24fa25a9e3e3ae685f2000685f01cae42d1653f
Reviewed-on: https://gerrit.libreoffice.org/20639
Reviewed-by: Oliver Specht <oliver.specht@cib.de>
Tested-by: Oliver Specht <oliver.specht@cib.de>
|
|
Change-Id: Ib8d0e3d240e693c678d575b4791f69ca760919ec
|
|
Change-Id: I5f35e0aeb6cef5920891eaa338c1d9b29e0ce554
|
|
Change-Id: I7141510fbda1158511698f73c48274008f0a41dc
|
|
Change-Id: I5a8daa1c0f2b62dbf56fa9fc1d14555f0ff613e2
|
|
Change-Id: Iada331a12232fd83b6813e6db65bd011d3746142
|
|
Change-Id: I962544005b5d408f7c044a02eefe09b87d8a81fe
|
|
... and fix the breakages it finds.
Change-Id: Ibc7289cc0cd7fb5648d686bd55afff9016f58b3b
Reviewed-on: https://gerrit.libreoffice.org/20638
Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
Tested-by: Jenkins <ci@libreoffice.org>
|
|
Change-Id: Iebf7b44e78fc28c20bdf0cbea84dbfd730b04016
|
|
Tooltips change on state change, and they were taken from another source.
Unify this to reuse the existing strings from the uno command.
Change-Id: I8ff6fc43bc0469f15c9e930695d950f6d664bfdf
Reviewed-on: https://gerrit.libreoffice.org/20629
Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Tested-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
|
|
when used as a mutable data-structure. Plain std::vector halves the time
taken to display the chart dialog
Create a class to represent the std::vector we are going to be passing
around, and move some of the utility methods into it to make the code
prettier.
Also create an optimised append(&&) method for the common case of
appending small temporaries.
Change-Id: I7f5b43fb4a8a84e40e6a52fcb7e9f974091b4485
|
|
With this, a reader can actually find them in the table stream. Mark as
experimental till all the related structures are written, so Word
doesn't consider the file corrupted.
Change-Id: I3f997dcdb14557b1f8eed78bd873b121068d9712
|
|
Change-Id: Icd719c461613f8c59cad81b256678307f69974e1
|
|
Change-Id: I4a08016859b0afa95d8bf3a42be41bbe72c31570
Reviewed-on: https://gerrit.libreoffice.org/20623
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Oliver Specht <oliver.specht@cib.de>
Tested-by: Oliver Specht <oliver.specht@cib.de>
|
|
Change-Id: Idf82c1d7f1b5e149c3796f5999fd09cf2c31299f
Reviewed-on: https://gerrit.libreoffice.org/20603
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Oliver Specht <oliver.specht@cib.de>
Tested-by: Oliver Specht <oliver.specht@cib.de>
|