https://bugzilla.redhat.com/show_bug.cgi?id=1436077
--- Comment #18 from Mike FABIAN mfabian@redhat.com --- (In reply to fujiwara from comment #17)
Thinking this again, maybe 0xfe0e and 0xfe0f are enough instead of 0xfe00 - 0xfe0f.
I'd liked to ask pango people about the following suggestion. --- pango-1.40.4/pango/pango-context.c.orig 2017-03-30 19:03:28.081488378 +0900 +++ pango-1.40.4/pango/pango-context.c 2017-04-04 13:35:18.446935865 +0900 @@ -1404,6 +1404,15 @@ itemize_state_process_run (ItemizeState { shape_engine = NULL; font = NULL;
}
/* If an emoji font does not include emoji presentation, let
* harfbuzz handle the characters.
* http://www.unicode.org/emoji/charts/emoji-variants.html
*/
else if (G_UNLIKELY (wc == 0xfe0fu || wc == 0xfe0eu))
{
shape_engine = NULL;
font = NULL; } else {
Yes, this works, it makes the fully-qualified emoji sequences work for me!
For example for this fully-qualified sequcence for the male golfer
🏌️♂️ U+1F3CC U+FE0F U+200D U+2642 U+FE0F
works for me (= renders as a single glyph) only when using the above patch, without that patch is is rendered as several glyphs.
Without that patch, only the non-fully-qualified sequence
🏌♂ U+1F3CC U+200D U+2642
works.
As using the fully-qualified sequences is recommended I think that patch is needed.