Created attachment 80926 [details]
Test file showing the broken behaviour
Writer seems to always consider the point of text direction change (i.e. from RTL to LTR) a valide break point, even if it isn’t otherwise. In the attached file the first paragraph is broken after the opening parenthesis (end of RTL run) because it is follwed by digits (start of a LTR run). Replacing the digits with Arabic letter in the the second paragraph prevents the unwanted break point, as expected.
Win 7 64-bit Version: 220.127.116.11.alpha1+
Build ID: 8b21b5cbe78945b27525b4ce78ae3d981f90590f
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-06_03:55:51
On Linux, I confirmed with 4.3 and 4.5, but not on 3.3 or 3.5. Thus marking as a regression.
Ubuntu 14.10 64-bit Version: 18.104.22.168.alpha0+
Build ID: f92183833fa569006602ac7e93c906d2094e0d4d
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-12-14_00:21:45
Build ID: 430m0(Build:2)
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Was able to replicate the issue but not find a bibisect version where it worked. Tested back to 3.5, location set to en_US.
Migrating Whiteboard tags to Keywords: (preBibisect)
*** This bug has been marked as a duplicate of bug 56408 ***