-
Notifications
You must be signed in to change notification settings - Fork 302
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
Emoji ⚠️ is not shown as emoji #450
Comments
Hi @muuvmuuv It's happening because we added a To prevent it from happening you need to modify the font files. Delete the warningSign But here is a link to StackOverflow with other options https://stackoverflow.com/questions/12976424/how-to-remove-characters-from-a-font-file |
What is the advantage of using this Emoji? |
It isn't that mandatory for me so that I am willed to spend the time on modifying the font, but thanks for the hint, good reading! The advantage for me and other project members would be that the yellowish Emoji stand out much more than the grey symbol. |
- Added Control code support #241 - Update all # dependent glyphs #275 - Added Ɛ ↋ ↊ ૪ #356 - Changed the look of ~@ ligature #415 - Added EMQuad (u+2001) #439 - The tail of Italic “f” made shorter #441 - Reworked⚠️ #450 - Added SemiBold weight #453 - Added more anchors to the marks #463 - Added replacement (u+FFFD) #461 - Added zeroWidthNoBreakSpace (u+FEFF) #467 - Fixed consistent of J in italic
Increased the size of |
Hi, |
@fpopineau there is a good article about emoji https://tonsky.me/blog/emoji/ Especially see Variation selector-16 part |
Thanks for the detailed information.
Unfortunately, it seems that the variation selector 16 is not supported
under Windows 10/11 :-/
Le sam. 30 juil. 2022 à 19:00, Alexey Ten ***@***.***> a
écrit :
… @fpopineau <https://github.com/fpopineau> there is a good article about
emoji https://tonsky.me/blog/emoji/
Especially see *Variation selector-16* part
—
Reply to this email directly, view it on GitHub
<#450 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOTV3ZH5QST7YAM6BBXXBTVWVNRRANCNFSM45UECGBQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Fabrice
|
I'm pretty sure it works on Windows, but it may not work in some applications. |
Oh... I said that it is not supported because I found it on
https://emojipedia.org/microsoft/windows-11-november-2021-update/variation-selector-16/
but I have no idea of the reliability of this source.
Actually what I see on this page
https://www.ii.com/unicode-variation-selectors-15-16/ makes me think it may
be supported (or at least partly ?)
So I played with it but I still don't understand if what I see with
JetBrains Mono is correct or not.
I duplicated one of the rows to add an example with entity ⚠
Then I changed the font-family for <p>
With JetBrains Mono I see :
![image](https://user-images.githubusercontent.com/1915631/182036785-c29c3995-3aec-42ff-bced-1bc30d67e709.png)
With Source Code Pro (and many other fonts not providing the
… I'm pretty sure it works on Windows, but it may not work in some
applications.
—
Reply to this email directly, view it on GitHub
<#450 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOTV3ZWOPBTFDSUHR4CIK3VWYSDBANCNFSM45UECGBQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Fabrice
|
@fpopineau images in your answer are missing. Please answer from github website. |
Sorry. I have edited the message above. |
Looks like Chromium-based browsers have a bug https://bugs.chromium.org/p/chromium/issues/detail?id=964527 |
The latest EAP supports variation selector 15/16 for emoji characters. https://youtrack.jetbrains.com/issue/JBR-4832/Support-Variation-Selectors-in-text-rendering-for-emojies |
Using the Emoji "⚠️ " in VS Code just displays a Unicode Symbol, even with a fallback font:
I am aware that there was a previous discussion about monospaced fonts should not include Emoji support, but then why is this happening, and how can I prevent it?
The text was updated successfully, but these errors were encountered: