No-brake space not working with Asian font text or mixed Western and Asian font text.
Steps to reproduce:
1. Create a new Writer document.
2. Copy the following text and paste it in the document: 范围从20至100mm成层
3. Shrink the document width with the horizontal ruler to any position within '100mm'
Result: No line break in '100mm'.
3. Insert a no-break space between '100' and 'mm' with Ctrl+Space or the Special Characters dialog (U+A0)
4. Insert a no-break space between the last two Chinese characters '成层'.
Result: The line will break between '100' and 'mm' or between the 2 'm' or between '成层' when you reposition the ruler.
Expected result: No line break in a Western string with a no-break space or between any characters that are linked with a no-break space.
Version: 126.96.36.199.alpha0+ (x64)
Build ID: abcc4eb907661e07ad850ccce7eb06f129da4286
CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win
Locale: de-AT (de_AT); UI: en-US
I confirm it with
Version: 188.8.131.52.alpha0+ (x64) / LibreOffice Community
Build ID: f96004096268f5e71120678e32fc8c74055819aa
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Not exactly surprising, as the default line-breaking rule for (modern) Chinese is "anywhere but some special place before/after punctuation marks", as we don't use spaces to separate "words" at all. And new exceptions to this rule had to be introduced when Latin-and-Chinese mixed text layout was considered.
It's probably not hard to fix though, one just needs to treat non-breaking spaces not as whitespace character when considering line-break positions.
It would be interesting to know if the same problem exists for Korean texts, as they use spaces to separate words. Japanese doesn't (just like Chinese) and presumably is also affected.
Dear Thomas Lendo,
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 https://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://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Still existing with 184.108.40.206