Age | Commit message (Collapse) | Author |
|
Change-Id: I919f5f0c4f6a1f6b1ea6261d9703da7a6c1046d3
|
|
Change-Id: Ibaf2211425ff2ab6fc7647c159ec6b1f095e843a
|
|
See commit 94855fbbb977d6acd42c32e157af664d0ede9739 for rationale.
Change-Id: I34838ea9dd60f24d20ac48e6089915b506f5d790
|
|
Change-Id: I8da1e43ffe6a78f14ab0901ae73c4ee39f1cbe44
|
|
Change-Id: I6d0b45451c8fe232afc05041d3c70a98e8bd8cc8
|
|
If a paragraph has its own <w:numPr>, do not let <w:pStyle> override that.
Change-Id: I7cea0d1c8bf59804f8c56382ee68c7fad5ed3ef6
|
|
Change-Id: I32317a1a6500377f7e7bb98d1dcc65ad86feb9a2
|
|
Word uses a completely different definition of "width" of a double border
than OOo and ODF: for Word the width is apparently the largest of the 3
component widths, while OOo and ODF define the width as the total with of
all 3 components. The new border implementation in LO 3.4 was apparently
inspired by Word's double border definition, which resulted in
various import filter regressions, see the previous fixes:
36e43b52992735c622833e923faa63774b9e2f76
e2ffb71305c5f085eec6d396651c76d6daee3406
70a6a4d425558340bb49507975343a3e0a1bdde8
These fixes set the ScaleMetrics, which actually seems sub-optimal as
there is a ScaleItemSet function somewhere that apparently re-scales
all items in an itemset, which could undo the fixes.
Also, one of the fixes actually managed to break RTF/DOCX import
of double borders, as that ended up in the same code via the API.
This commit now reverses the change, so that the width of a border is
now always the total with of all components, which is (imho) much more
intutitive, and also leads to a consistent UI where selecting say 3pt
width has predictable results, no matter what the border style.
The border widths are now converted in the Word format import/export
filters (writerfilter and sw/source/filter/ww8), and various tests
were adapted to the new handling.
Change-Id: I50456c49b1a298569607e6c88f19f18441348ac3
|
|
... not to the tables::BorderLineStyle values, because the domain
mapper's MakeBorderLine converts the values to BorderLineStyle.
Change-Id: Id89e0bcf80fbd9a1ac9238e09d898bb6b82303b4
|
|
Change-Id: I1dadb53f46b23f92d34061ef78dda872bdbcda67
|
|
Change-Id: I0d6aad17c471b6edd584c668dc7ff054090c185c
|
|
Change-Id: Ia817624647ba395476d457ccd1681c6a82534e5a
|
|
Change-Id: I04ef6ffefa7e27a1f9cac6d7d46cb6022223b9ff
|
|
Change-Id: I7d1d7d8c5f8291defb86f205ea0d65674493b467
|
|
Change-Id: Ib303edb8962b70727624ff44a8bb957e10362529
|
|
Change-Id: I2f51f4709e8f92fd6779e8e59227e82ac335050b
|
|
Change-Id: I4ac1056582a41dd2bc5c31452c93122afd666fc7
|
|
Some of them were commented out for documentation purpose.
Change-Id: I29a6b2cbe774b527f0c3a0be5675160817a7f3ce
|
|
|
|
Change-Id: Icb531e05f84c8ce7e79a15113102113be3609f45
|
|
Change-Id: I5a6fd4c8fcb2641cdceabcd58c3fa0ccae059d25
|
|
Change-Id: Ib7c76768e302556a88ae6d87770c57f31ea8d36b
|
|
Change-Id: I71580bb77b6939c9294eaf5203431d32327d5efd
|
|
Change-Id: I9d695f9b544250017bea69167e3133c4e9ee37a4
|
|
Change-Id: Ic36b131ee9964a6671f7f41e1cad1631c43ad565
|
|
Change-Id: Ib4ba76d0083e5bd75cc589a55318089c004f591f
|
|
Change-Id: I14369787e99d31cba32957301340cef2fc832b91
|
|
Avoid some uses of non portable #!/bin/bash in shell scripts.
Patch contributed by Pedro Giffuni
http://svn.apache.org/viewvc?view=revision&revision=1235297
|
|
This commit reverts the fix for fdo#44176, and implements a better fix,
which keeps the original testcase passing, but also fixes the layout of
a simple document, having different first, odd and even headers within
the same section.
Change-Id: I96893ce3e886e479f1d7640b126ad7a1dd828bdb
|
|
Change-Id: I9e108f278a82f2ff8d4e5a29fa8af7c58843e9e4
|
|
|
|
The problem was that a continous section break at the end of the
document caused the section margins to be ignored. Just ignoring the
continous section break (only in case it's at the end of the document)
makes the problem go away.
The original fix was commit cd1c434c4bd4756fa1355e906cb2e8de4aae0618,
but it got reverted in commit 2dee7d6205832a1212790ac1ab168a6b6fce686d,
as it caused fdo#44292. This second attempt fixes the original bug
again, without introducing the "4 columns" bug.
Change-Id: I75d612430a5cd631dec0d224127cba580070900d
|
|
Change-Id: I1eb5946d23cd3ff635d436adbd59bf007333aa60
|
|
Change-Id: Ia6e097f9f93bcfe14392f5ef0245994752001f6c
|
|
Change-Id: I4623dfd05498b5ba8de73b7e301eaf486f667738
|
|
This reverts commit eae88a9cb1120aecf2e296277778fb22a70a62dc. Need to
find a better fix, this breaks the ooxmltok unit test.
|
|
Change-Id: I5eaf8b765d03b898c1c9a466802b75bbfe05a622
|
|
Change-Id: Ib06d88890007fd27d6838a5c8829230733d3df97
|
|
The docx spec doesn't say what is the default value, the rtf spec says
it's 720, not 1440.
Change-Id: Icb331591d4f2f96a7786f808d99af5974e645f8e
|
|
Change-Id: I8018d9b5fa01d1720c0392dc5fdc4a0656f25a35
|
|
Change-Id: I6c145e984c885c7e06caa1c27bfb354ea49ad9ce
|
|
w10:wrap was originally arrived to
writerfilter::dmapper::WrapHandler::lcl_attribute(), but
writerfilter::dmapper::DomainMapper_Impl::PushShapeContext() was called
already and set the anchor type. Fix this, then we can set a a suitable
anchor type in lcl_SetAnchorType() based on the type model.
Change-Id: Ib411450b10f29f814bc13d81eaec434971b2e52a
|
|
Change-Id: Ice06e639213aeb6f7f23cbf4634947dd25613db1
|
|
Change-Id: I514828469e68f2ae88309418e64ee93be30455f3
|
|
Change-Id: I71c3ebfcb68a53a291bcab2fdd397d62fd8b368a
|
|
Word handles the "border to page" distance as a subset of the page
margin. Writer handles these values separately, and the real margin is
the sum of the border width, the margin and the border width itself.
The problem was that the width of the border itself wasn't counted, so
the real margin was a bit larger than necessary.
Change-Id: Id38153308f1e321b6556762b30f3377f2360edf6
|
|
Change-Id: Ie0ed609076d59fbb9f3209e406de76aaa731073e
|
|
Change-Id: Ib8e9976e618e676465f0baf1f38be7e3297ac853
|
|
Change-Id: I707105f6da53a6cb790d743738875acde561e20f
|
|
This way the sprm handlers can be aware that a numbering is provided by
that style.
Change-Id: I5b5f1570a9e50fd8b3372f5ac7a6cd48e9751254
|