Created attachment 118895 [details] Example for ignoring non-breaking spacesin fields If you cross reference to a text with non-breaking spaces, this non-breaking spaces will be handled as "normal" breaking spaces in the resulting field. This is ugly if you reference to non-breaking-spaced names like "E. Domingos de Sousa" or "C. H. Schulz" an the result is "... E. Domingos de Sousa" or "... C. H. Schulz"
Thanks Stefan. Confirm the behaviour. (Imagine you've just learned someone of Non breaking spaces and the next step is reference fields ;\ ) See the same in version 3.3.0
The same happens when you have a header based on the Chapter. A non-breaking space in the chapter text will be a normal space in the header. I get a header like this: Stephanie - Chapter 13: Two Dinners, a Send Off and a Business Plan, Part I Ugly!
** 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-20161108
Bug still present in Version: 5.5.0.0.alpha0+ Build ID: 5c16d16ed3db32f922b2aeaad49592d2615c7e2c CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-05-26_23:00:41 Locale: de-DE (de_DE.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
This bug is still present. Version: 6.2.1.2 Build ID: libreoffice-6.2.1.2-snap1
*** Bug 129853 has been marked as a duplicate of this bug. ***
*** Bug 145824 has been marked as a duplicate of this bug. ***
Still present in Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Might be treated as duplicate of bug 39754.
Still present in 7.5.0.3
*** Bug 161316 has been marked as a duplicate of this bug. ***
Hi, I am not sure if my reported bug 161316 is really a duplicate, as I also mentioned problems with non-breaking hyphen and LOST(!) TEXT in cross-reference et the end of line in that bug, which are not mentioned in this bug. I also provided an example file in bug 161316, which I also put here. I think this bug (or Bug 39754) should be expanded also in the description to be clear about all parts of the bug, so that the LO team can handle all the problems in one step. And I would like to add that this bug has not been fixed since 2015 (almost 9 years), which should make it a priority, as LOST text is a critical bug in my opinion. Still present in version: 24.2.3.2.
Created attachment 194472 [details] test file.odt
Created attachment 194473 [details] test file.pdf