<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN: DOCX: slow opening" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135245#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN: DOCX: slow opening" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135245">bug 135245</a> from <a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> Justin L</a> <pre>Well, in these test documents, there truly are a TON of nested frames for the page numbers - as seen in the ODT's styles.xml. So almost certainly the first commit from author Zolnai Tamás on 2014-02-16 17:35:14 with commit 05955dd2096c29853f831d5d16b86c7b7ca00b28 DOCX export: nested text frames In Word it is not allowed to anchor a shape to another shape. That's why this code write text boxes only on the first level, nested frames is also written out on the same level because writeDMLText/WriteVMLText will push nested frames into m_aFramesOfParagraph's back. is the reason for the "multiplication" of frames seen in the header. So I'm not sure any of this could be considered a bug (except for the design of the original document). (In reply to Gabor Kelemen from <a href="show_bug.cgi?id=135245#c5">comment #5</a>) > Loading many drawing shapes is slow. Well yes - this known problem can be considered a problem, and these example documents are good proof of that. I imagine there is a bug report about that already.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>