RFR: 8246104: Some complex text doesn't render correctly on macOS

[Phil Race]

On Fri, 2 Jul 2021 18:29:12 GMT, Phil Race <prr at openjdk.org> wrote:

>> They are in there. But with the current approach for CT glyph-parsing, I see no other way. The parsing is done in native code (e.g. OS.CTLineCreateWithAttributedString()) but we extract the required font from the returned runs, e.g. 
>> `String fontName = CTFontCopyAttributeDisplayName(actualFont);`
>> Next, the `fontName` is searched for, but if it is not in the "public" list of fonts, this fails. So if we don't make these dot fonts public, this approach doesn't work.
>
> When you say "public" you mean in the lists that the implementation searches for a match ?
> This could get tricky. I don't have a complete answer off the top of my head.
> Could we at least filter the returned list of full and family names to exclude them ?
> Then explicit searches would work but no one will be seeing them in a list of fonts available to apps.

the filter would be macOS only and exlude fonts with a name beginning with "."

-------------

PR: https://git.openjdk.java.net/jfx/pull/547