I used macOS 10.12.3 and I got the same cascade list for Menlo-Italic as
Prasanta mentioned (with .AppleSymbolsFB substituted and .NotoSansUniversal
omitted in Java code).
If it's not possible to add .NotoSansUniversal now, some Unicode ranges,
apart from Arabic, will still remain not covered in
Hi Phil,
I was using osx10.11 but the list I enumerated in JBS is actually the
composite font I get in CCompositeGlyphMapper#convertToGlyph() which
contains those 29 slots
[CCompositeGlyphMapper#convertToGlyph(unicode=value 1575) gets the glyph
code(909) from slot[4] which is CourierNewPSMT,
Hi,
I don't know what versions of MacOS X either of you (Dmitry+Prasanta)
used but I am going to guess they are different
(can you both report these, for the record).
In https://bugs.openjdk.java.net/browse/JDK-8147002, Prasanta enumerates
the cascade list for the Italic case and I don't see
> Yes, we are aware this fixed it only for Oracle JDK.
> The bit I missed is that GeezaProInterface was then used on OpenJDK by
JRS.
> So we could add that as well.
> If you have any other fonts you think should be added to the tail of that
list we
> can add them too.
I ran
Hi Prasanta,
Changes are fine.
Thanks,
Jay
-Original Message-
From: Prasanta Sadhukhan
Sent: Friday, February 10, 2017 10:32 AM
To: Prahalad Kumar Narayanan; Philip Race; 2d-dev
Subject: Re: [OpenJDK 2D-Dev] [9] RFR JDK-8147002:[macosx] Arabic character
cannot be rendered on MacOS X
--
Message: 1
Date: Thu, 09 Feb 2017 19:09:00 -0800
From: Philip Race <philip.r...@oracle.com>
To: Prasanta Sadhukhan <prasanta.sadhuk...@oracle.com>
Cc: 2d-dev <2d-dev@openjdk.java.net>
Subject: Re: [OpenJDK 2D-Dev] [9] RFR JDK-8147002:[macosx] Arabic
character cannot be
santa Sadhukhan <prasanta.sadhuk...@oracle.com>
Cc: 2d-dev <2d-dev@openjdk.java.net>
Subject: Re: [OpenJDK 2D-Dev] [9] RFR JDK-8147002:[macosx] Arabic
character cannot be rendered on MacOS X
Message-ID: <589d2ecc.4090...@oracle.com>
Content-Type: text/plain; charset="utf-8"; Fo
I am OK with this if you can confirm that removing Lucida Sans Regular
from the JDK does not cause any nasty exceptions.
Apple use the PostScript name but our lookup code should work for the
TrueType name.
So overall I think this should be fine - from visual inspection - and
assuming it has
