https://bugs.documentfoundation.org/show_bug.cgi?id=164500
--- Comment #6 from Justin L <[email protected]> --- This is my understanding of the situation. We import the text and stick it into text nodes as simple paragraphs, tracking the start and end nodes (range) of the similarly framed paragraphs. At some point we notice the frame changed. Then we issue a convertToTextFrame. -the convert creates a frame -copies the text nodes into the frame -sets the anchor point to the start of the copy range -deletes the copied range. (So now the anchor point [which hasn't moved nodes] is pointing to the "next paragraph" after the now-deleted copy range.) At this point the next paragraph is also just a simple paragraph, since convertToTable has not yet been called. In these cases it is a textnode that will become the first paragraph of the first cell. But there is no way that unotext can know this at this point. And when we convertToTable, there is no reason to suppose that any anchored stuff is NOT supposed to be in a table. So I guess I need to just force a new node at the end of the framePr range. AFAICS, LO does not allow a frame to be anchored to a table startnode, but in MS Word that appears to be possible. So this is emulation which will end up with an additional paragraph (that might put things out of perfect alignment). -- You are receiving this mail because: You are the assignee for the bug.
