Bug Hunting Session
Bug 80000 - A no-break space or non-breaking hyphen prevents a preceding valid line break opportunity
Summary: A no-break space or non-breaking hyphen prevents a preceding valid line break...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Formatting-Mark
  Show dependency treegraph
 
Reported: 2014-06-13 19:51 UTC by Simo Kaupinmäki
Modified: 2019-12-03 14:16 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
A set of test cases (14.09 KB, application/vnd.oasis.opendocument.text)
2014-06-13 19:51 UTC, Simo Kaupinmäki
Details
A set of test cases (14.09 KB, application/vnd.oasis.opendocument.text)
2014-06-13 19:53 UTC, Simo Kaupinmäki
Details
LibO 4.3 vs Word 2010 (148.53 KB, image/png)
2014-06-14 00:32 UTC, Yousuf Philips (jay) (retired)
Details
A set of test cases (5.06 MB, application/vnd.oasis.opendocument.text)
2016-05-28 08:05 UTC, Simo Kaupinmäki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Simo Kaupinmäki 2014-06-13 19:51:49 UTC
Created attachment 101005 [details]
A set of test cases

In some situations, a no-break space (U+00A0) or non-breaking hyphen (U+2011) prevents a valid line break after a normal hyphen (U+002D, U+2010) or dash (U+2013, U+2014) or soft hyphen (U+00AD) that occurs within the preceding word. Specifically, this only seems to happen if the preceding word is also the first word in the paragraph (which means that the issue is unlikely to emerge unless the paragraph begins with a long word or string and the line is rather short).

Reproducible: always
Found in LO 3.5.4.2 (on Debian stable), 4.2.4.2 (on Windows), and 4.3.0.0.beta2 (on both Debian and Windows)

As a workaround, you could use a narrow no-break space (U+202F), a combination of word joiner (U+2060) and normal space (U+0020), or a combination of a regular hyphen (U+002D) and word joiner.

Note: this issue looks similar to bug 58477 but only occurs in a very specific situation. I also occurs on Windows, and in LO 3.5.4.2 and 4.3.0.0.beta2, which are not affected by 58477.
Comment 1 Simo Kaupinmäki 2014-06-13 19:53:58 UTC
Created attachment 101007 [details]
A set of test cases
Comment 2 Yousuf Philips (jay) (retired) 2014-06-14 00:31:40 UTC
Confirmed in Linux Mint in 3.3.0, 4.2.4 and 4.3 beta.
Comment 3 Yousuf Philips (jay) (retired) 2014-06-14 00:32:12 UTC
Created attachment 101022 [details]
LibO 4.3 vs Word 2010
Comment 4 tommy27 2016-04-16 07:27:38 UTC Comment hidden (obsolete)
Comment 5 Simo Kaupinmäki 2016-05-28 07:59:08 UTC
The bug still affects LibO 5.1.3.2 on both Linux (Debian Jessie backports) and Windows.

Version: 5.1.3.2
Build ID: 1:5.1.3-1~bpo8+1
CPU Threads: 1; OS Version: Linux 3.16; UI Render: default; 
Locale: fi-FI (fi_FI.utf8)

Version: 5.1.3.2
Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: fi-FI (fi_FI)
Comment 6 Simo Kaupinmäki 2016-05-28 08:05:38 UTC
Created attachment 125339 [details]
A set of test cases
Comment 7 Xisco Faulí 2017-09-29 08:50:45 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-12-03 14:16:17 UTC
Dear Simo Kaupinmäki,

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