Age | Commit message (Collapse) | Author |
|
Change-Id: Id006db1013c981a6f2392bb52c2f26cf5e5bae5d
|
|
Change-Id: I24af395c6899e9b3551bd7ff473ada2315812173
|
|
Change-Id: Ia019c93841043ac5d65e08ad17400acc27f82d6c
|
|
Change-Id: If13c1ce4847e5711cbb60196a77a669411496306
|
|
Change-Id: Ib1058fcc10100938a34fae18e94fa9fd21ebfb36
|
|
Change-Id: Iae638fbc5142e7c6d3f62bd6916b25fa4ecf040e
|
|
Change-Id: I81205ae7010ab776cd1880f779af2f623e290da9
|
|
Conflicts:
sw/qa/extras/ooxmlimport/ooxmlimport.cxx
Change-Id: I7efd68fe21dddd7d9262d3e0b7400db67504e6bc
|
|
Problem Description: In case of multicolumn sections, separator line was getting added during export to docx.
Unit test cases added to verify the code changes.
Change-Id: Id65ac4d3878eed298882c85082cec9575f914d83
Reviewed-on: https://gerrit.libreoffice.org/6211
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
|
|
Change-Id: I435f2781be620fa910a40a49fde19ecc81a70974
|
|
Change-Id: I7bd0fb541f16e39400b40742e92b501be086c887
|
|
Change-Id: I0b203dd65f659533dd3db9f25a1d42569473df31
|
|
Change-Id: I475bee35ca5d24903d85e7f2427fab0e47d8db4d
|
|
Change-Id: I6b8d728011c2b70061dbdcdc3daba37422f99306
|
|
Change-Id: I721fbbd7bcf33b6ab3535170afbf68e520134850
|
|
Change-Id: Ic84ac4d58e14c3bc59d902ce535566cc7e59a5d8
|
|
Change-Id: Icc20bb1de73c119efdb9dd80f35cdb9f2d342529
|
|
Change-Id: I7be21f126eddc6e49649ea3370a7a181d976360b
|
|
PropertyDefinition was introduced long ago, probably in order not to have to
touch larger amount of code when it turned out that it was necessary to store
more information in PropertyMap - otherwise even then it was more logical to
extend the value from uno::Any only to some structure.
PropertyMap's API itself is quite non-convenient, it is half-way between
direct access to the std::map it is derived from, and something built on top
of that.
In the long run I believe we want to make _PropertyMap member of PropertyMap,
not an ancestor, and change the API; if anybody cares enough, that is ;-)
Change-Id: Ib8e9bfc4561f003b78ab6ce6620722e251f661d6
|
|
Change-Id: I8a989f4a4faab3e611d4a04ef5a00ac4921d2f7c
|
|
Change-Id: I201985753fc53f037807e7870c6786a442717d6e
|
|
Change-Id: I7526953ba1f4d95cb550be13df6616cb6046e518
|
|
Change-Id: Ie8efc727ef903c0f578e774a03385d3e9422b80c
|
|
Change-Id: I7fb12f9f612ab55a5b41e24dcd1952dbfbaa6ad4
|
|
Change-Id: Ia06a2436fd7d13c544cdf78bbd6bdb0d0c0f900e
|
|
Just store them in the document InteropGrabBag for now.
Change-Id: Ia413930746ed087bcb0f6e338198c7baa5bcbdf0
|
|
Change-Id: Ic9f653f31b64b55bba128f983c560e9064235ce6
|
|
its the same result either way, but seeing as the assignment
is duplicated might as well tidy it up
Change-Id: Id64547c6a5d2ce58b1ee79ba64cb761575b2d1dd
|
|
Also add vim modeline, that represents the current whitespace convention
used in this file.
Change-Id: I8faae4f211125695bd686fd9f09430530e4ae91c
|
|
Change-Id: I6fbf2034632bea432848e99474c82ccff0e0565c
|
|
Change-Id: If362d80a86a7493f2d43e6d661b94fc03942711f
|
|
Change-Id: I2db5102fbc441c0b79d8c28023f3e3bb5613b3cf
|
|
Regression from 2ade07126971b79c92f729fae5709f2e2e2b495c (fdo#62044 RTF
import: don't overwrite existing styles when pasting, 2013-06-04),
during paste, if existing style was found, then the intention was to
skip that style, but instead we tried to create one.
Change-Id: I83adaf9fe6b8a578fa60c21b9463fabde7707d7e
|
|
This was introduced in commit 9c7ffb6b61f7c94ca5b38d11be1807f1e29ff4bc
([cbosdo03]Applied the patches to upstream, 2009-12-02), as setting the
outline level also set the NumberingStyleName to "Outline" as well,
which is not what we want.
Since then, commit b95d203bc17c83ec0fe5139f519d53ed1d842d3a (Don't load
the default values of the styles in writerfilter, 2012-08-20) already
disabled default styles, so the previous manual clearing is no longer
necessary (testcases already fail if this later commit is reverted).
As a result, just remove this manual clearing, it's no longer necessary
and it is problematic, as it triggers copying the SvxLRSpaceItem from
the parent style with no good reason.
Change-Id: Ie17547a979a6b0feadbd2eed0f06e84fcb17fca6
|
|
Change-Id: I0885168291aa3ffa9500e1e5543c725a118c8ddf
|
|
Change-Id: If4b4f0144b6c8926b0f3962b2d7db9c74768b0da
|
|
Since 78d1f1c2835b9fae0f91ed771fc1d594c7817502, we convert floating
tables to text frames only in case it's possible that there will be
wrapping, to give better results for multi-page tables, which are
multi-page, and technically floating ones, but that has no effect on the
layout.
The problem was that we try to do this decision too early, effectively
the page width and margins were counted from the default letter size,
instead of the actual values, which did not arrive at the time of the
decision. Fix this by moving this logic at the section end.
Change-Id: Ic1fbceb54c8ec223ed01836fafe6220bb3b2410a
|
|
Steps
-Add a new character attribute (RES_CHRATR_HIGHLIGHT)
-Get this character attribute via SwFont class just like
background
-If has highlight, then paint that, otherwise paint background
-Extend UNO API
-Implement DOCX export and import filter
Note: By now character highlight can't be set via UI.
It's a next step to add a highlight option.
Change-Id: I7f81e173744bf256891487f898d06dbf372a2f88
|
|
And hopefully this will also fix the Windows build as well.
Change-Id: I6a008c0bf74d436be7eef0c5d0945dd07e3954e5
|
|
Change-Id: I27dc30c8aba7b77cdac771ca733fadb805a5c75b
|
|
Writer core doesn't support this, and this has been a problem for table
cells as well. There the workaround we're using for quite a while is to
do the rotation at a text portion level instead, which results in
reasonable layout for simple cases. Do the same here.
One additional complexity is that the API between oox and writerfilter
is a single UNO shape, we get this property in oox, and we have to
handle it in writerfilter, when the text frame is already attached to
some text. Kill this problem by adding a FrameInteropGrabBag for sw text
frames: it's useful anyway, and then we can pass around this property
inside the grab bag.
Change-Id: Idb5ec83b5cbdde8f29d15b2cebfad24226bb6507
|
|
move .doc combined character parser stuff from sw to filter for reuse in .docx
and fix bad length problem when nSavPtr == -1 after String->OUString conversion
thanks for the pasta CloudOn
Change-Id: I368ca30c14fd089271902b9b874de1099eb40038
|
|
Change-Id: I0a996ce1b8cd520ddf3911bc80923b20a28fa1a4
|
|
Change-Id: I9d15ae93f807b6b3723b728ec10bf05e249c75ad
|
|
Change-Id: Ia62e4b458a0f374015da20c06fcc67bfece91574
|
|
Change-Id: I7915021745d2d99e1cec882ca2928e932dbffbef
|
|
Change-Id: I3ecbcabd0b379ff520346a163e0eea7bc0d2f8f9
|
|
Change-Id: Id100e3cc13b1d694af40b1b5d789cf90736593fa
|
|
Change-Id: I800b9b3af13df7faf1f7636a6be1941572328d25
|
|
Change-Id: If1d2a3a33490d522b59cbba2317c42856dd60f7b
|