Created attachment 122239 [details] Illustration Space Bug sample When adding a caption to an image, an invisible space is added at the beginning of the caption, before "Illustration 1.2: FooBar". This can only be seen when creating a cross reference or in the index. A sample document has been attached to show this effect. This bug has only appeared since the 5.x releases. I've used several of them and most if not all show this behaviour. To fix this problem, go into the caption and press delete with the cursor placed before the "I" of Illustration.
Hello, and thank you for bringing this issue to our attention. I was not able to reproduce this issue with: Version: 5.0.4.2 Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale: en-US (de_DE) But I was able to reproduce with: Version: 5.1.0.2 (x64) Build ID: ecd3574d51754b043f865cf5bafee286d24db7cc CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: de-DE (de_DE) The issue was introduced somewhere in between, probably with the change in how illustrations are referenced. In 5.0.4.2 it takes the form of "Illustration <n>: <caption>" While 5.1.0.2 changed it to " <n>. Illustration: <caption>", note the space To reproduce in 5.1.0.2: 1. Open new Writer document, insert any image. 2. Right-click on image -> "Insert Caption..." 3. In the new window, insert any text for caption, choose any properties, click "okay" 4. Put the writing cursor into any valid line and "Insert -> Cross-reference..." 5. In the new dialog: Type: Illustration, Insert reference to: Reference, click "Insert" 6. The new reference has a leading space I'm setting this issue to NEW, but I'm not sure if this was an intentional choice or not. In the meantime, a valid workaround might be not use a manual leading space and just let the reference touch against the previous word. The grey background will not be visible in print and the automatic space will not be noticeable. Because of this I will be lowering this issue to TRIVIAL. -- Windows 10 Pro, Version 1511 (OS Build 10586.36)
I agree that it is a trivial bug. A case where the work-around does not work is in indexes and if a sentence is started with the reference. This is especially noticeable if some of the captions were created with earlier versions of LO. Out of curiosity, why was the change made?
** 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.2.5 or 5.3.0 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-20170306
I can confirm that this is still an issue in 6.0.6.2 (Windows x64). Although strangely, sometimes it seems like it is not an issue, because other captions I created yesterday do not have the extra space, for no apparent reason. I can't recall doing anything different to those other images/captions. I certainly didn't delete the invisible space.
I hope that this problem can be treated as more than trivial. I am working on a chapter with many figures. All of the captions I created directly from screenshots have this space in the cross-reference list. Figures created in other ways do not have the space. The lack of consistent order in the cross-reference list has been driving me crazy. Now that I finally have some understanding of what is causing the problem, I need to manually delete the spaces in many figures. That is not how I should be spending my time. Note that this is not just an issue for illustrations. I hope that someone is willing to solve this problem.
(In reply to Cathy Crumbley from comment #5) > I hope that this problem can be treated as more than trivial. > Trivial does not mean that the issue is trivial. Issues marked as trivial indicate issues that are trivial to solve. This is one of those issues which might be solvable by someone who is new to LibreOffice programming.
Ah, thank you for clarifying, Andreas.
I can't confirm it with Version: 7.3.2.1 (x64) / LibreOffice Community Build ID: 0b2e59a88b7e225b655db87910f97dca7aef27aa 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 and attachment 122239 [details]. So it seems to be resolved. => RESOLVED WORKSFORME Feel free to change it back to NEW with a short reasoning, if you disagree. Additional information: I can see a space between top of the image and caption border, but I think this report doesn't refer to this problem, that is reported in bug 147770.