Proposal: Deduplicate `u1f46a` by aliasing it to `u1f9d1_200d_1f9d1_200d_1f9d2` in `emoji_aliases.txt`

[hohoDigidea]

I would like to suggest optimizing the repository by utilizing emoji_aliases.txt to deduplicate identical glyphs.

The Proposal

Please add the following line to emoji_aliases.txt:

1f46a;1f9d1_200d_1f9d1_200d_1f9d2

And subsequently remove the image asset emoji_u1f46a.png (and .svg), or replace it with a placeholder image to indicate that this emoji does not need to be designed. (I have verified that the build script will prioritize the alias mapping defined in emoji_aliases.txt even if the file exists, making the placeholder approach a safe and effective way to signal this.)

Reasoning

1. Visual Consistency: Both u1f46a (Family) and the sequence u1f9d1_200d_1f9d1_200d_1f9d2 (Family: Adult, Adult, Child) are universally treated as identical in the Unicode standard and other major vendors.

2. Asset Organization: I recommend keeping u1f9d1_200d_1f9d1_200d_1f9d2 as the source ("to") and aliasing u1f46a ("from").

• The long sequence naturally groups with other four family combinations in the file system, and they share the same iconic design language.
• u1f46a is isolated in the file list and surrounded by different style images.

3. Benefit for Third-party Contributors: Since this repository is a reference for many open-source projects, keeping two separate image files creates a "trap" for third-party designers. They might assume the two emojis require distinct designs (e.g., one realistic vs. one iconic) because the files are separate. Aliasing them explicitly signals that these emojis are intended to be identical, reducing workload and preventing design inconsistency.

Although emoji_aliases.txt currently contains only flag mappings, I checked the build scripts and verified that it supports mappings for other emojis as well. This change would result in a cleaner repo and clearer semantic intent.

References

https://unicode.org/emoji/charts/full-emoji-list.html