Created attachment 76623 [details] docx file demonstrating differing word wrap in Word and LO Attached is an example Word document (produced on Mac OSX) demonstrating a bug that produces different line breaks when opened in LibreOffice. Such differing line breaks ruin the overall layout of a shared docuument between Word and LO. I have attached the .docx file (lo_bug_page_break7.docx) and pdfs showing the correct output (lo_bug_page_break7_word.pdf) and LibreOffice output (lo_bug_page_break7_LO.pdf). Note that on opening the Word file in LO, you should select all text then set the font size to 12 (due to a different bug (reported) some fonts are set to size 16 in LO)). If you show hidden characters and turn on maximum zoom in LO, it appears that the cases of differing word wrap occur when a hidden character extends well beyond the end of the line (whereas Word would wrap in that case). Also, the first line is an example where Word will not break a two Word field from EndNote whereas LO will. The last line is a negative example that displays teh same on Word and LO despite white space appearing to slightly overlap the page margins. The Word version the file was open on was: Word 2008 for Mac Version 12.3.1 and the LbreOffice version was: Version 4.0.1.2 (Build ID: 84102822e3d61eb989ddd325abf1ac077904985) TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time: 2013-02-27_17:15:43
Created attachment 77083 [details] Another word wrap example Another example of different word-wrapping between Word and LO. This example shows that hyphens in the text can lead to different word-wrapping. lo_word_wordwrap_bug2.docx is original Word document; lo_word_wordwrap_bug2_word.pdf shows the output of Word; lo_word_wordwrap_bug2_lo.pdf shows the output of LO. Word and LO versions as in the previous example.
Some additional information- even if I first save the file as a doc file in Word and then load the doc file with LO the word wrap differences are still there, so this appears to be a bug in the underlying word wrapping algorithm.
Thank you for reporting this issue! I have been able to confirm the issue on: Version 3.6.5.2 Platform: Bodhi Linux 2.2 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well. Marking as: New (confirmed) Normal - prevents high quality work and interoperability with MSO is broken High - this is quite serious and makes it so that working with docx files creates inconsistent results. CC'ing Michael Stahl Michael - Want this one? + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
In LO 4.4.1.2 on OSX there has been no change- the examples show the same bug.
Migrating Whiteboard tags to Keywords: (filter:docx)
** 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
Repro 6.4+. Many bugs on this. Related to Microsoft font rendering, TNR here.
Dear brian.bj.parker99, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug