Commit Graph

7 Commits (9572d1c70e1136a8f4e9b1aef3c7601bfd9bdaab)

Author SHA1 Message Date
Rod S 565d292c31 Unicode 13.1 update 2020-09-16 13:23:48 -07:00
rsheeter 546287c772 Emoji 13 assets 2020-07-20 13:33:17 -07:00
Doug Felt b1246768db Update png images for unicode 11.
These were regenerated from source and most have rather imperceptable
differences, only a few are genuine modifications.
2018-08-09 16:50:11 -07:00
Doug Felt fe2ced8501 Re-add PNGS which were accidentally deleted.
A previous commit intended to remove the old PNGS and just leave the
new ones, but neglected to add the new ones resulting in the deletion
of all the PNGs.  Um... oops.
2017-08-27 10:37:06 -07:00
Doug Felt e2a1cbe3c4 Remove 'aliased' PNG images that were in the previous style.
The update to the new design accidentally left some old images.  The new
design doesn't include resources for images we alias, and when the
directory was updated I forgot to remove the images corresponding to the
aliases.
2017-08-25 17:09:09 -07:00
Doug Felt 69b0092a76 Update PNG resources to the new design. 2017-08-25 13:55:18 -07:00
Doug Felt b9cbe2324c Use full sequences to name images for mixed-gender couples.
We currently name the mixed-gender 'kiss' and 'couple with heart'
images after the single-codepoint sequences.  But aliasing maps
the single codepoint sequence to the gendered sequence, not the
reverse.  As a result the build doesn't create ligatures for the
gendered sequences, since it thinks the image doesn't exist.

Fix this to use the gendered-sequence-names for these images, and
let aliasing work as intended.  This follows the convention we've
adopted of letting the name more completely describe the image
contents, and defining how to represent less-specific sequences
using aliasing rather than baking these decisions into each image
name.
2017-03-06 16:02:24 -08:00