[Libreoffice-bugs] [Bug 116270] FILEOPEN: Tables in Word document overlapped (follow-up of bug 94598)

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Jun 3 12:20:19 UTC 2020


https://bugs.documentfoundation.org/show_bug.cgi?id=116270

Justin L <jluth at mail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME
                 CC|                            |vmiklos at collabora.com

--- Comment #6 from Justin L <jluth at mail.com> ---
fixed in LO 7.0 by commit fd7749fddc5a767461dfced55369af48e5a6d561
Author: Miklos Vajna on Fri Feb 14 16:29:44 2020 +0100
    sw: fix handling of table vs fly overlaps in the AddVerticalFlyOffsets case

    When a table overlaps with a fly frame, Writer creates a fly portion
    inside the relevant cell frame (increasing its height), and Word shifts
    the table down. Both are valid approaches, but the rendering result is
    different in case the table has a border.

    So keep the default unchanged, but in case the AddVerticalFlyOffsets
    compat flag (set by the Word importers) is set, avoid the overlap the
    Word way.

    Note that the table frame uses the full width (available in the body)
    even for e.g. 50% width tables, so check for the overlap using the print
    area, which does not always overlap.

    Finally, don't always require a valid frame area definition from the fly
    frame:

    - the mentioned i#46807 bugdoc currently doesn't need that check

    - the fly frame area definition becomes valid only after already
      positioning the table, leading to an overlap

    Keep that check for the non-compat case, though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200603/5d9c0b9c/attachment.htm>


More information about the Libreoffice-bugs mailing list