diff options
| author | Miklos Vajna <vmiklos@collabora.co.uk> | 2017-07-11 12:44:56 +0200 |
|---|---|---|
| committer | Tamás Zolnai <tamas.zolnai@collabora.com> | 2017-07-12 03:30:50 +0200 |
| commit | 40c420adf77fc6dd41306dcd1fdf2ce06b456a80 (patch) | |
| tree | 39503dcecff93d86e6a5129a8d9fcd361b2fd69b /writerfilter | |
| parent | 91ca088171d58339715358b8a47f7adc491ba7fa (diff) | |
tdf#109063 DOCX import: consider wrap space for multi-page floattables
Follow-up to commit 78d1f1c2835b9fae0f91ed771fc1d594c7817502 (fdo#68607
bnc#816593 DomainMapperTableHandler: don't always start a frame,
2013-09-03), turns out in case there is little space between the table
and the edge of the body area, then there is no wrapping performed in
Word, so we should not convert to floating table, either.
The limit seems to be 266 twips (mm100 unit is used in the code), and
this seems to be constant: it does not change if both the table and the
page width is changed, nor does it change when the empty paragraph to be
wrapped has a different paragraph mark size.
For the majority of the documents this means no change as usually there
is either no space available for wrapping or there is a lot more
available.
(cherry picked from commit 25445d24cfa87522ee4c47e4aa7e6e816cdc9a36)
Conflicts:
writerfilter/source/dmapper/PropertyMap.cxx
Change-Id: Ibbf7409065ba958854514f23b360be56677c8fe3
Reviewed-on: https://gerrit.libreoffice.org/39828
Reviewed-by: Tamás Zolnai <tamas.zolnai@collabora.com>
Tested-by: Tamás Zolnai <tamas.zolnai@collabora.com>
Diffstat (limited to 'writerfilter')
| -rw-r--r-- | writerfilter/source/dmapper/PropertyMap.cxx | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/writerfilter/source/dmapper/PropertyMap.cxx b/writerfilter/source/dmapper/PropertyMap.cxx index c8cf96bb1f7f..89492db7f002 100644 --- a/writerfilter/source/dmapper/PropertyMap.cxx +++ b/writerfilter/source/dmapper/PropertyMap.cxx @@ -1102,7 +1102,11 @@ bool SectionPropertyMap::FloatingTableConversion(DomainMapper_Impl& rDM_Impl, Fl // If the table is wider than the text area, then don't create a fly // for the table: no wrapping will be performed anyway, but multi-page // tables will be broken. - if (nTableWidth < nTextAreaWidth) + // It seems Word has a limit here, so that in case the table width is quite + // close to the text area width, then it won't perform a wrapping, even in + // case the content (e.g. an empty paragraph) would fit. The magic constant + // here represents this limit. + if ((nTableWidth + 469) < nTextAreaWidth) return true; // If the position is relative to the edge of the page, then we always |