Created attachment 98770 [details] shows 3 occurances of space after periods larger in word 2010 than LibO I download the .docx file found at < http://download.microsoft.com/documents/uk/partner/publicsector/DraftMicrosoftResponsetoGovernment.docx > and opened it in LibO and saved it as an RTF. I then opened the RTF in LibO and word 2010 to compare them and noticed that multiple times in the file when there are two spaces after a period, word 2010 would show more space then LibO. I then opened the original .docx file in word 2010 to compare them and when i checked the font properties of the double space, word 2010 had 'kerning for fonts 12 points and above' enabled in the RTF. This was tested in Linux Mint on the last releases from 3.6 to 4.2 and 4.3 alpha.
Not sure what to make of this. Attaching a screenshot with clearer indication of what is being discussed. The place in question has two spaces after the dot (as Jay described already). For me they are displayed very similar in Word 2011 and LO 4.2.4.2. So maybe just a Linux issue? Jay, maybe I misunderstood the issue?
Created attachment 98807 [details] better screenshot of what is being discussed
(In reply to comment #1) > Not sure what to make of this. Attaching a screenshot with clearer indication > of what is being discussed. You did show clearer identification of the issue but you didnt zoom in enough to clearly show a comparison. > The place in question has two spaces after the dot (as Jay described > already). For me they are displayed very similar in Word 2011 and LO > 4.2.4.2. So maybe just a Linux issue? Jay, maybe I misunderstood the issue? Well i'm not sure of the RTF implementation in mac ms word, but you should right-click into font properties of the paragraph to see if the 'kerning for fonts' is set (will attach a screenshot of this). Its not a linux issue as i've also tested it in word 2013 on windows 7.
Created attachment 98812 [details] word 2013 showing the font properties dialog
Created attachment 101668 [details] Comparing LibO 4.4 and MSO 2010 Seems to work with Version: 4.4.0.0.alpha0+ Build ID: bdd87b2acddb2e244569dcc8f228e270614dc59e TinderBox: Win-x86@39, Branch:master, Time: 2014-06-23_00:37:24 on Win7 x64
Created attachment 101682 [details] rtf exports from word 2013 and LibO 4.4
Created attachment 101685 [details] word 2013 pdf export of the 2 rtf files
This issue is still not fixed. Version: 4.4.0.0.alpha0+ Build ID: e62764108a1832e746f68768c29eaa90606903a7 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-06-20_22:05:17 I checked the old OO 3.3 rtf export and it has the same issue as the new export.
Created attachment 101856 [details] Test doc picture with non-printing chars enabled
Congrats jay, found a MS Office bug :)
Created attachment 101871 [details] Word RTF vs LibO RTF in Word 2013
Created attachment 101872 [details] Word RTF vs LibO RTF in Kingsoft Writer
Just to reiterate this is an RTF save issue as shown in both Word 2013 and Kingsoft Writer screenshots. I checked Wordpad and it doesnt show the additional spacing, but that is likely because its not a full featured word processor. :)
Reproducible, tested using Mac OSX 10.9 with LibreOffice Version: 4.4.0.0.alpha0+ Build ID: eddd7646d672ea9b0561dacb09da224d098e531e TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2014-07-18_06:13:47 Document opened using Word for Mac 2011. Kind regards, Joren
** 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.0.5 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: 2015-09-03
Migrating Whiteboard tags to Keywords: (filter:rtf ) [NinjaEdit]
** 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.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Created attachment 136639 [details] trimmed sample
So i checked the binary of the double space and it turned out to be no-break space (\x0a) and a regular space (\x20). Issue still present. @Miklos: could you give your input on this. Version: 6.0.0.0.alpha0+ Build ID: 13df3777e4b6ff7537692b396be67a5fd2b9b001 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
** 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
Created attachment 177855 [details] The last example files RTF versions made by Word 2013 and Writer master opened in Word Still an issue in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: eb69767d7c1bb8e6e780fd9503f08c9d7f5ecb45 CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded Kerning is not enabled anymore, but something else makes it still bad in Word. There is no such visible difference between the two files when they are opened in Writer.
Dear Yousuf Philips (jay) (retired), 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