<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Repeat Table Heading Suddenly Appeared" href="https://bugs.documentfoundation.org/show_bug.cgi?id=119369#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Repeat Table Heading Suddenly Appeared" href="https://bugs.documentfoundation.org/show_bug.cgi?id=119369">bug 119369</a> from <a class="email" href="mailto:miscellaneous@paintdrawer.co.uk" title="DM <miscellaneous@paintdrawer.co.uk>"> DM</a> <pre>Created <a href="http://bugs.documentfoundation.org/attachment.cgi?id=153236" name="attach_153236" title="Repeatable Example">attachment 153236</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=153236&action=edit" title="Repeatable Example">[details]</a> Repeatable Example The attached example shows the problem in a repeatable way. Go to p15 and delete the carriage returns above Holly Blue, save and reopen - you will find all the arrows and labels completely mangled. I found also in moving them back (or creating new ones) and resaving, they just jump back again but adding CR before that table makes them ok. Much of the time they have not been repeatable, yet happen all the time, because you often only discover on reopening the document or when you look further down the document and find an impact. This isn't the only problem. In general, I'm using pictures in table cells with drawing elements (arrows and text boxes) and they are constantly mangled by all sorts of processes - moving something somewhere else in the document (you discover later the mangling), moving the table (particularly cut and paste - dragging to a new place seems to be much much safer). It's far worse when you have a single table so I am using 1 or 2-row tables that are separate and this 'contains' the mangling to individual tables and allows reordering the tables by drag-and-drop without wrecking the drawing elements in the document so much. I have to take a PDF snapshot all the time, so I can check every day etc what gets mangled and fix it back. In terms of quality level the bug puts tables-with-drawing-objects as not fit for production, but I am using Libreoffice because it can export without quality loss, so I can put little insets which people can zoom into on a PDF program. Version: 6.2.5.2 (x64) Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>