Repository navigation
v0.5.2
This release makes the fallback of text choose an emoji font for an emoji that the first font does not draw as an emoji (D40).
go get github.com/xo/okage@v0.5.2Fallback
- A character with U+FE0F, the selector that asks for the emoji form, now falls back to an emoji font when its font has no color glyph for it. For example, with Noto Sans first, "©️" and "™️" now draw with the color emoji font, as a browser draws them. A plain "©" stays in the text font.
- An emoji sequence that a font draws as several glyphs, because the font has no ligature for it, now falls back to a font that draws it as one emoji.
- A run that has only such a cluster to fix stays in its font. Only that cluster moves to the emoji font.
The fallback ranks each cluster as missing, not emoji or drawn, and takes the glyphs of a fallback font only when they rank better. An emoji sequence is found by ranges of characters (U+FE0F, U+20E3, the tags and U+1F000 to U+1FAFF), because go-text keeps its emoji data in an internal package. This is a deliberate difference from upstream. It applies to ShapeText and to <text> elements. When resvg changes its fallback, okage removes the code of D39 and D40 and ports the change of upstream, as D40 says.
Upstream
okage now follows resvg up to 5bdbae64, the release of resvg v0.50.0. That commit changes only versions and the changelog.