Created attachment 91859 [details] text get missing in older doc file As you can see, both MSO and LO support linked textbox, where text can flow from one box into the other. With doc files, everything works fine if not perfect, until the textboxes are GROUPED. Depending on the MSO version, the file in question is saved with, grouped and linked text boxes may get UNLINKed in different ways, in some case the text is missing in a unrecoverable fashion, which is worse than messed layout. For doc files created from MSO 2003 and previous, the text flows are broken into corresponding grouped but unlinked text boxes in LO. This could have been acceptable for viewers. But this breaking process consumes 1 character each time it breaks a text flow, which means every previously linked textbox got one trailing character missing, except the last box. And there doesn't seem to be a way to recover this missing text in LO along. (see attachment for example ) For doc files generated by MSO 2007 (and above?), Grouped Linked Textbox got unlinked, and all the text is crammed into the first textbox in LO. Other textbox got empty. Besides the first textbox is expanded vertically for as long as necessary to avoid text overflow, which messed up the layout. With docx file , all linked textbox are broken in LO. The Grouped ones are merged and enlarged horizontally in a uncontrolled way beyond the page border. Not grouped but linked ones become empty except the first textbox with overflowed text hidden. As you may have noticed in daily publications, linked textbox is a very basic and common tool in desktop publishing. And missing text is a real deal breaker. We really need it to work correctly. Please fix this feature in doc format. Thank you, Wilson.
Created attachment 91860 [details] MSO 2007 linked textbox sample
Created attachment 91861 [details] MOS2007 linked textbox sample (doc)
Created attachment 91863 [details] MSO 2003 Linked Textbox sample English text looks alright, since only white space and line-breaker is bitten off. But when double byte Characters get bitten off like with white-space and paragraph line-breaker, we start missing text with CJK lanugage.
This is in no way a blocker - changing priority. Blockers are really for incredibly serious problems like inability to install or crashers that will affect most users.
I reproduce with the doc & docx. Win 7 64-bit Version: 4.4.0.0.alpha1+ Build ID: 56019dcb79475606952a954fe732a3109441ffec TinderBox: Win-x86@39, Branch:master, Time: 2014-10-30_07:27:11
*** Bug 87348 has been marked as a duplicate of this bug. ***
anyone here knowing if this did work properly before??
In Bug 87348 I marked it as pre-bibisect. For the .docx part of this bug at least, it appears that it has never worked. Just verified (using bug 87348 sample LinkedFramesBug.docx) that docx doesn't flow on versions: -oldest (3.5.0): doesn't really support textboxes at all. -last36onmaster: 3 textboxes shown - all text in the first box -last40onmaster: no textbox or text seen at all -last41onmaster: same as 3.6 -last42onmaster: same as 3.6 -last43onmaster: same as 3.6
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Created attachment 137131 [details] tdf73499.6alpha1.pdf - PDFs of the three test docs still incorrectly rendered by LO6.0 alpha1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The issue with textboxes not grouped fixed in bug 87348. Grouped textboxes are still not working in Version: 6.2.0.0.alpha0+ (x64) Build ID: 5e8cd8683d345b75297994b3f7aab851835eb124
Let's track the .docx issue here. The .doc issue exposed by attachment 91861 [details] was spun off into Bug 120755.
Created attachment 178438 [details] How it looks in Writer 7.4 (resaved in mso) This ticked has two cases: 1) VML groupshape (v:group) with linked feature >> still missing feature, but VML deprecated 2) DrawingML equivalent (resaved with word 19) >> Works with patch, as in my screenshot (Gerrit: https://gerrit.libreoffice.org/c/core/+/130283)
Created attachment 178439 [details] The bugdoc resaved version
Fixed for DOCX in https://gerrit.libreoffice.org/c/core/+/130950. For DOC, there is a workaround to convert it to DOCX/DrawingML by MSO, so I suggest to close this issue, and file a new one for DOC, if needed. @Attila: thanks for the fix! @Wilson, Buovjaga, Justin, Luke: thanks for the bug report and bug handling!
Attila Bakos (NISZ) committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f81800193a942b3f68c61a5cede634f3eeb47b1f tdf#73499 DOCX import: fix grouped linked textbox It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified in: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: a3988b2d147a2442b348d58b79dbd6e71472b7af CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded