-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unicode 16.0 #88
Comments
Ok, i will wait. (i am too excited.) |
I've decided I'm going to create U+1FAE9 Face with Eyebags |
The eyes aren't as low as seen in https://www.unicode.org/L2/L2023/23236-esc-report-q4-2023.pdf, which is what I accomplished. I was planning to use the frowning mouth asset from U+1F641 but it didn't look good, which is what you seem to be using in your revision of U+1FAE9 although the mouth is a bit modified from the original. |
ok 😀, but still using the revamped? |
|
maybe i should make my own version of twemoji |
no one's stopping you from making and maintaining your own fork of twemoji tbf |
here's the unicode document that mentions this btw |
There's several errors in this image:
|
i draw bad |
wait do you draw the emojis with a pencil tool instead of placing nodes and whatnot? |
Yeah because I don't know what is nodes |
Nodes are the dots that make up the path (aka the shape) object. |
ohhhhhhhhhhhhhhh |
well i don't know how to shape splatter |
i guess i'll do it |
nvm i give up (i cant draw it either) |
May 21st: the page “Emoji Recently Added” has been updated: With sample images from Noto Color Emoji |
google's tired face looks so goofy |
i am with you |
Did you notice that the
|
Any updates on the release of Twemoji 16.0 now that Unicode 16.0 is out? Is everything finalized? |
@Mercury13 Design of Sark flag Source: https://github.com/Mercury13/unicodia/blob/main/NotoEmoji/Remakes/Flags/C/1f1e8-1f1f6.svg |
The codepoints have been accepted as seen in this revised document |
I can't create ANYTHING in Inkscape 😭 |
I've created an SVG for the Sark flag by combining elements from flag: England and flag: St. Pierre & Miquelon |
SOMEONE MAKE THE ORCA |
@yutose what i like to do is optimize the svg file on svgviewer.dev, then check all of these optimization preferences shown below (or you can check off "remove viewBox" to get what you're asking for) |
|
it really got big |
Landslide is bad: it displays fur tree instead of rocks falling. |
I'll change it later
…On Tue, Dec 31, 2024, 5:59 AM Mercury13 ***@***.***> wrote:
Landslide is bad: it displays fur tree instead of rocks falling.
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOCJDYABHH5RKA4MEXD4G532IHF3LAVCNFSM6AAAAABFMANGW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHE4DQNBVGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
WHY DID YOU SAY MY LANDFILL IS BAD
…On Tue, Dec 31, 2024, 5:59 AM Mercury13 ***@***.***> wrote:
Landslide is bad: it displays fur tree instead of rocks falling.
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOCJDYABHH5RKA4MEXD4G532IHF3LAVCNFSM6AAAAABFMANGW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHE4DQNBVGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Because it does not fulfil the task of emoji. You don’t see falling rocks, you see a hill and a tree. And it’s a landfill (i.e. the place you bury garbage in), not a landslide (a natural disaster). |
ohhhh |
Better but…
|
Where is it written? I checked all the repo and found nothing. If you show me the palette and guidelines, I’ll try to squeeze to them. |
Hello folks! Unicode 16.0 is currently being worked on by Unicode's Emoji Subcommittee (current draft proposal). It is expected to be released in the second half of 2024. When Unicode 16.0 is finalized, we'll track the designs of each newly added emoji here. Emoji that have been approved so far for 16.0 are listed below, taken from Unicode's Emoji Recently Added (16.0) list.
The text was updated successfully, but these errors were encountered: