Bug 169585 - Layout: Miscalculations for References
Summary: Layout: Miscalculations for References
Status: RESOLVED DUPLICATE of bug 39754
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Formatting-Mark Fields-Cross-Reference
  Show dependency treegraph
 
Reported: 2025-11-21 03:45 UTC by b.
Modified: 2025-12-30 03:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Document to demonstrate the issue. (20.98 KB, application/vnd.oasis.opendocument.text)
2025-11-21 03:47 UTC, b.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description b. 2025-11-21 03:45:10 UTC
Description:
Referencing a Header leads to:  
1.) not obeying non-breaking-spaces, 
2.) dropping the part after the non-breaking-space,  
on some situations / positions.  
  
See attached document, inserting a space after "listening so far" wraps the "1" of "Appendix 1" to the next row, despite the space is a "non-breaking",  
inserting two more spaces also wraps "Appendix", while dropping the non-breaking space and the "1". 

Steps to Reproduce:
see above.  


Actual Results:
breaks text,  

Expected Results:
keep content and respect formatting.  



Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 24.8.5.2 (X86_64) / LibreOffice Community
Build ID: 480(Build:2)
CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Debian package version: 4:24.8.5-2
Calc: threaded  
  
If relevant: running on a 4k screen,  started with:  
GDK_SCALE=2 SAL_FORCEDPI=256 libreoffice --writer  
  
Same effect in safe mode.
Comment 1 b. 2025-11-21 03:47:00 UTC
Created attachment 204156 [details]
Document to demonstrate the issue.

Document to demonstrate the issue.
Comment 2 Dieter 2025-12-29 12:44:46 UTC
As far as I can see unfortunately a very old bug, that hasn't been resolved sofar

*** This bug has been marked as a duplicate of bug 39754 ***
Comment 3 b. 2025-12-29 15:53:36 UTC
@Dieter: thks for caring / investigation,  
@all: very impressive bug resolving speed ...  
is there any "oldest unresolved" competition around that I missed?