Created attachment 519929 [details] Test file with embedded tricky CJK fonts Description of problem: Some 'tricky' CJK fonts requires the use of formerly patented byte-code interpreter to be rendered properly. Version-Release number of selected component (if applicable): freetype-2.2.1-28.el5_5.1 How reproducible: Always Steps to Reproduce: 1.Open attached 'tricky-cjk.pdf' in evince Actual results: The glyphs of the CJK characters are misplaced, resulting in malformed characters. Expected results: The glyphs of the CJK characters should be shown properly. Additional info: The use of patented BCI is required to render those CJK fonts, but the patent has recently expired, and freetype-2.4.4 enables BCI by default.
Created attachment 519938 [details] Backport support for tricky CJK fonts to freetype-2.2.1 The attached patch backports the changes in http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b972a2a294a6d1f53ad403ae2bf0a098a38f0c2b&h=master to provide support for tricky fonts. This patch also incorporates checksum-based tricky font detection from http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=9f5dd61bf3deee315da14d3aca7f436bbf9cc76a . The attached patch depends on the freetype-2.1.10-enable-ft2-bci.patch in the SPEC file, which is not used by default. However since those CJK fonts must use the patented BCI, and that patent has now expired, the BCI patch should always be applied (just as patented BCI is always enabled in freetype >= 2.4.4).
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).