Skip to content

Conversation

@felifluid
Copy link

This is the pull request for the addition of queer symbols as discussed in detail in #572.

The new queer symbols are added to the non-unicode section openmoji-extras in a new subcategory queer-symbols. It reserves the private use area codepoints E420–E460.

Note that this PR copied the transgender emoji πŸ³οΈβ€βš§οΈ to the new codepoint E421. That means it can be used as a singular unicode symbol, instead of using 1F3F3-FE0F-200D-26A7-FE0F (🏳 β€’ VS16 β€’ ZWJ β€’ ⚧ β€’ VS16) to create it. However, it think it's important to include the trans flag redundantly in these two different ways in order to ensure compatibility.

I wasn't able to run the tests, as installing with npm failed on my machine (will look into that). So would be great if someone else can run those prior to merging.

Fixes: #572 and #587

@b-g
Copy link
Member

b-g commented Nov 20, 2025

Hi @felifluid, many thanks for this! Currently it does not pass the tests ... I think it would be really easier if you could find a way to run the test locally. Otherwise it will be a lot back and forth. Once you've added/edit the meta infos in data/extras-unicode.csv, do the following:

  • run npm run generate-data-tables to generate the files in data folder eg. openmoji.json
  • then npm run test-dev β†’ if green, please PR :) ...

Also we don't have any way to have redundancy and aliases. Hence for the transgender emoji either a breaking change (moving it to E421, I would vote for that) or leaving at 1F3F3-FE0F-200D-26A7-FE0F. We have in every release breaking changes, once existing openmoji-extras become included to the most recent Unicode.

@felifluid
Copy link
Author

Also we don't have any way to have redundancy and aliases. Hence for the transgender emoji either a breaking change (moving it to E421, I would vote for that) or leaving at 1F3F3-FE0F-200D-26A7-FE0F. We have in every release breaking changes, once existing openmoji-extras become included to the most recent Unicode.

Just for clarity: How would the current transgender emoji "πŸ³οΈβ€βš§οΈ" be displayed after this change? Would it be displayed as "🏳⚧"?

@b-g
Copy link
Member

b-g commented Nov 20, 2025

@felifluid Yes. The current transgender emoji (the src svg file) will simply be renamed and moved to the new location in queer-symbols. Hence in future releases 1F3F3-FE0F-200D-26A7-FE0F will point to no src file and will either result displaying the "missing glyph" symbol or "🏳⚧" depending on the context. Basically users will have to update to the new codepoint E421.

The transgender emoji has been moved to extras-openmoji/queer-symbols/E421. This breaks the unicode transgender emoji "πŸ³οΈβ€βš§οΈ", instead the new codepoint "" has to be used.
@felifluid
Copy link
Author

@b-g All issues should have been resolved now. The old transgender emoji was removed, including the entry in data/enhancements-emoji-unicode-data.csv.

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

Successfully merging this pull request may close these issues.

Proposal To Add Pride Flags πŸ³οΈβ€πŸŒˆ

2 participants