Skip to content
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

:no_good: is replaced by πŸ™…β€β™€οΈ instead of πŸ™… #179

Open
eramdam opened this issue Jan 17, 2024 · 8 comments
Open

Comments

@eramdam
Copy link
Contributor

eramdam commented Jan 17, 2024

Like the title says πŸ˜…

This is reproducible on the demo

image

At first I assumed it was a regression I caused in my PR for emoji 15 but it seems to be caused by the no_good and woman-gesturing-no equivalence?

Perhaps the issue lies in https://github.com/iamcal/emoji-data itself? πŸ˜…

@eramdam
Copy link
Contributor Author

eramdam commented Jan 17, 2024

According to https://projects.iamcal.com/emoji-data/table.htm, the equivalence shouldn't be there in the first place πŸ˜…

@iamcal
Copy link
Owner

iamcal commented Jan 18, 2024

This is working as intended.

In the original source data, :no_good: maps to U+1F645 ("FACE WITH NO GOOD GESTURE").

However, this codepoint has been obsoleted by 1F645-200D-2640-FE0F ("WOMAN GESTURING NO") when Apple (and then other vendors) added the gendered versions of these emoji.

This data (the obsoletes/obsoleted_by fields) is not shown in the HTML table, which adds to the confusion.

At present, this behavior is not optional. It would be pretty easy to make a preference to allow it to be ignored and the original codepoint chosen instead (the JS code in question starts with if (self.obsoletes_data[out.full_idx]){)

@eramdam
Copy link
Contributor Author

eramdam commented Jan 19, 2024

But then is there a way to output πŸ™…? Or are consumers of the library expected to catch this case to work around it? πŸ˜… (I see Slack properly translates :no_good: to πŸ™… for example).

Or are you saying that making the obsolete-related behavior optional would allow to :no_good: -> πŸ™… conversion to happen as "expected"?

@eramdam
Copy link
Contributor Author

eramdam commented Jan 19, 2024

And I guess the issue happens in reverse in that using replace_unified with colons_mode = true with πŸ™… produces :woman-gesturing-no: which feels like a bug?
image

@iamcal
Copy link
Owner

iamcal commented Jan 19, 2024

I'm saying that adding such a flag would keep the old behavior (from before gendered emoji replaced the neutral ones). Given that Apple has since back-tracked on the change and added back the gender neutral versions, this is probably a better default.

@iamcal
Copy link
Owner

iamcal commented Jan 19, 2024

PR #182 makes your desired behavior the default

Working on making it actually work :D

@eramdam
Copy link
Contributor Author

eramdam commented Jan 19, 2024

I'm saying that adding such a flag would keep the old behavior (from before gendered emoji replaced the neutral ones). Given that Apple has since back-tracked on the change and added back the gender neutral versions, this is probably a better default.

Gotcha!

PR #182 makes your desired behavior the default

Thanks! πŸ™ I can try testing this in our project next week, or maybe it's a safe change? I admit I'm not aware of other cases of obsolete(d) gendered emoji πŸ€”

@eramdam
Copy link
Contributor Author

eramdam commented Jan 19, 2024

PR #182 makes your desired behavior the default

Working on making it actually work :D

Okay I thought i missed something when it didn't work in my (quick) testing :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants