JDK-7042148 : closed/java/awt/font/TextLayout/CheckLayoutLTR.java failed
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.text
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: linux_oracle_5.6
  • CPU: x86
  • Submitted: 2011-05-05
  • Updated: 2014-01-09
  • Resolved: 2011-08-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 JDK 8
7u2Fixed 8 b01Fixed
Related Reports
Relates :  
JDK-7050826 - Hebrew characters are not rendered on OEL 5.6
Description
see comments
Comments
Verified 8 b122 win 7, oel 5.8
09-01-2014
EVALUATION This is a bug in new Bidi implementation. Itelator.first() needs to be called first. In current implementation, getAttribute() is called before first(), and it is the cause of this test failure.
02-06-2011
EVALUATION I've attached "C.java" and the DejaVU font from OEL 5.6 It doesn't support Hebrew but the point is that the test passes on JDK 7 b61 and starts failing from right after the BIDI update.
27-05-2011
EVALUATION The failure seems to be triggered by some other changes. First in b134 the font configuration file for this RH/OEL release was removed, so that it falls back to the synthesised font properties file. Although I haven't yet figured out exactly which fonts are now being picked up instead that plays a role. But even using a particular font from OEL 5.6 that causes a failure of this test when used anywhere (eg Solaris), that failure in turn seems to start after b61 in b62, 63 or b64 (we've lost b62, b63 forever it seems) but as 6850113 : Bidi class needs to be updated to support Unicode 5.1 was in b62 I'm guessing it started then. So b134 changes unmasked a bug that actually goes back to b62.
27-05-2011