I maintain a Ruby gem that depends on Pango and we’ve had some regressive behavior over the last year regarding emojis on Windows.
It looks like pango replaces my font string with “emoji”, which silently falls back to Segoe UI no matter what I specify. Looks like this code in pango-context.c does that.
I can see that as of 1.43.0-1, in this commit that pango should read from the Windows registry. I have tried this with no success (and it appears to not be documented?). But I also know that my users won’t like hacking the registry for functionality that worked cleanly in the past.
For the short term: can someone explain to me how to hack my registry to get Segoe UI Symbol to get picked up? If I get it working I’d be happy to write it up for your docs.
For the long term: I see that pango-context.c now has structs for two different font descriptions: one for non-emoji, one for emoji. But the pango font string has no way of specifying the two different families. Is there a way (or can there be a way) to specify this via a font string?
For more context and test cases, I’ve been working with @kou on this on a GitHub issue: