summaryrefslogtreecommitdiff
path: root/instsetoo_native/util/openoffice.lst
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@suse.cz>2013-05-13 11:24:58 +0200
committerMiklos Vajna <vmiklos@suse.cz>2013-05-13 13:02:31 +0200
commite9485fb5c5453618a39c8b64f607346c77aabad6 (patch)
treefabd2105147e435f1cdde845a9cc86170e00352a /instsetoo_native/util/openoffice.lst
parenta4422e1c976d4d3f030671da13b765175439acbd (diff)
bnc#816603, fdo#61594 SwWW8ImplReader::StartApo: don't always start a frame
Word supports floating tables, Writer does not. We can map floating tables to fly frames, containing just a table, but then those can't span over multiple pages. We could avoid creating frames in case the table is of multiple pages, but that's hard to determine. One easy case is when the table width is >= the text area with, in that case we can be sure that no wrapping would be performed anyway, so we can avoid putting the table to a frame. Two more related problems: 1) When we need to decide if a frame should be created or not, we typically don't know yet the table width. That's why TestApo() has to always succeed (in case the paragraphs are wrapped), and then we always enter StartApo(), where we can avoid creating the frame, if necessary. 2) Even if we decide that we don't create a frame, floating and non-floating table rows are different, so a separate table should be created for such rows. By doing all the StartApo() / StopApo(), we are safe here. (cherry picked from commit c2cf03e02b1c942645aea6988112028e13dd0c89) Change-Id: Ifc0e0e2f7320c3784698d0ff278031b46864e2e5
Diffstat (limited to 'instsetoo_native/util/openoffice.lst')
0 files changed, 0 insertions, 0 deletions