Created attachment 86956 [details] the docx test file Problem description: A MS Word docx file was opened in LibreOffice. Some non-breakable spaces are not displayed correctly. Steps to reproduce: 1. Open testdocument.docx in LibreOffice. 2. Open testdocument.docx in MS Office. 3. Show paragraph marks and other hidden formatting signs in both applications. 4. Scroll down to the tables and compare how the spaces between the currency symbol and the amounts look like. 5. See encircled spots in the screenshots. Current behavior: In LibreOffice, the non-breakable spaces are insserted but not displayed. Expected behavior: There should be a space between the currency symbol and the amount.
Created attachment 86957 [details] missing spaces in LibreOffice
Created attachment 86958 [details] spaces visible in MS Office
issue confirmed in LibO 4.1.1.2 under Win7 64bit. set status to NEW
Actually, the character between the currency symbol and the amount seems to be a zero width space (U+200B). That's what it looks like in LibreOffice Writer if you have field shadings on. If you turn field shadings off (View > Field Shadings), zero width spaces become invisible (but they'll allow a line break after the currency symbol, which probably isn't what you want). I don't have Word available, so I'm guessing here, but the rectangular symbol in Word may be a surrogate symbol indicating that Word doesn't know how to render the character correctly (perhaps because it isn't covered by the font).
** 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 (4.4.1 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-07-18
still present in LibO 4.4.5.1 and 5.1.0.0.alpha1+ (x64) Build ID: 5a61d7f049a81d6e747d9d097f364ae45f58697b TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-07-16_01:06:26 Locale: en-US (it_IT)
same issue on LibO 3.3.3 and OOo 3.3.0 so bug is inherited from OOo
Well, as I said above, the characters are not no-break spaces (U+00A0) but zero-width spaces (U+200B), and they are rendered correctly by Libo. (In Word there is a handy way to identify an unknown character: if you position the text cursor right after the character and press Alt-x, the character is immediately replaced by its hexadecimal Unicode value.) What is strange is that MS Word shows the zero-width spaces as rectangles, but this seems a bug in Word (though I can't actually reproduce this using Word 2013 on Windows 7). Therefore, I think this one can be closed as NOTOURBUG. In case there were originally no-break spaces in the document which were then somehow converted into zero-width spaces when edited or resaved with Libo, please file a new bug for this.
Oh, of course the zero-width spaces are only displayed as rectangles in Word if the non-printing characters are made visible. Doh.
so the NOTOURBUG is correct?
Yes. There seems to be nothing wrong in the way these characters are displayed in Libo.
Also, if the non-printing characters are not made visible, the zero-width spaces are not shown at all even in Word. This is perfectly correct, as the zero-width space is inteded to be invisible (though it allows line breaking). Therefore I think the non-printing rectangles in Word are rather confusing, and Libo's rendering of these characters (though with field shadings on) is better.