Bug 164731 - wrong behavior of no-break space in cross-reference
Summary: wrong behavior of no-break space in cross-reference
Status: RESOLVED DUPLICATE of bug 39754
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-16 16:52 UTC by Orwel
Modified: 2025-10-15 18:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
test file (27.79 KB, application/vnd.oasis.opendocument.text)
2025-01-16 16:52 UTC, Orwel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Orwel 2025-01-16 16:52:29 UTC
Description:
If you use no-break space (Menu/Insert/Formatting Mark) in a text, which you Set as reference (Fields/Cross-reference/Type), the no-break space does not work correctly.

Steps to Reproduce:
1. Write text, turn on Fields shadings (Menu/View)
2. Set some cross-references 
3. Use normal space/no-break space
(see attachment, in my case affected referenced text: "..Pr No..")

Actual Results:
No-break space is:
1. not included in the referenced text, a normal space is used, which cause the division of the text to be put together
2. not shaded in set reference - text (which looks like broken reference text or 2 separate referenced texts)

Expected Results:
No-break space should be:
1. included in the referenced text, with no division of the text to be put together
2. shaded 


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.8.4.2 (X86_64) / LibreOffice Community
Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002
CPU threads: 16; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster;
Comment 1 Orwel 2025-01-16 16:52:55 UTC
Created attachment 198582 [details]
test file
Comment 2 m_a_riosv 2025-01-16 22:35:27 UTC
Looks like a duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=39754
Comment 3 Buovjaga 2025-10-15 18:09:09 UTC

*** This bug has been marked as a duplicate of bug 39754 ***