You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For broad adoption of EmojiTwo, not having ready-to-use assets of EmojiTwo is a major issue.
You should supply TTF variants of ready-to-use font files, preferably in layered COLR/CPAL format as opposed to SVG-in-OpenType. Especially for embedding in software this is important because of the fact that SVGiOT is generally larger and slower to render than COLR fonts. This would allow adoption in e.g. our Pale Moon browser project.
Of note, when creating TTF files, bitmapped glyphs should be avoided at all cost to avoid issues like Google's Noto Color Emoji has. Only use vector for optimal display at all DPIs and avoiding glyph metrics issues.
The text was updated successfully, but these errors were encountered:
For a good COLR/CPAL font we would need to touch and optimize almost all SVGs so they use nicely stacked elements of the same color. That is doable but not high on the list of priorities. This could perhaps also improve SVG-based fonts, but it could also severely disturb the logical order of the vector objects.
For broad adoption of EmojiTwo, not having ready-to-use assets of EmojiTwo is a major issue.
You should supply TTF variants of ready-to-use font files, preferably in layered COLR/CPAL format as opposed to SVG-in-OpenType. Especially for embedding in software this is important because of the fact that SVGiOT is generally larger and slower to render than COLR fonts. This would allow adoption in e.g. our Pale Moon browser project.
Of note, when creating TTF files, bitmapped glyphs should be avoided at all cost to avoid issues like Google's Noto Color Emoji has. Only use vector for optimal display at all DPIs and avoiding glyph metrics issues.
The text was updated successfully, but these errors were encountered: