i am still having some issues with emoji rendering. first i thought it might be a problem with my system fonts on my Linux Machine but it also happens on macOS.
tested on Chrome and Firefox on Linux and on Safari on macOS
i am still having some issues with emoji rendering. first i thought it might be a problem with my system fonts on my Linux Machine but it also happens on macOS.
https://emojipedia.org/flag-for-european-union/
and
https://emojipedia.org/rainbow-flag/
for example are displayed as 2 symbols. (see attached screenshots)
tested on Chrome and Firefox on Linux and on Safari on macOS
I don't think that I can do anything about it as that seems to be an Mastodon related problem.
For me it does only work in Mastodon FE.
When using Pleroma FE,Pinafore or Brutaldon I get exactly the same bug.
They do all use the native system emoji,Halcyon uses the Twemoji library and Mastodon uses Twemoji icons but an own code for rendering them.
First I thought it may be an Twemoji bug but it supports combined emojis (multiple unicode chars for one emoji) if the code is correct.
In the Mastodon API response the code seems to be wrong so that all but their own emoji parser think that this are two different emojis.
I don't think that I can do anything about it as that seems to be an Mastodon related problem.
For me it does only work in Mastodon FE.
When using Pleroma FE,Pinafore or Brutaldon I get exactly the same bug.
They do all use the native system emoji,Halcyon uses the Twemoji library and Mastodon uses Twemoji icons but an own code for rendering them.
First I thought it may be an Twemoji bug but it supports combined emojis (multiple unicode chars for one emoji) if the code is correct.
In the Mastodon API response the code seems to be wrong so that all but their own emoji parser think that this are two different emojis.
interestingly mastodon shows me the correct emoji when i use the default web interface.
and according to the Firefox developer tools the emoji comes correctly from the API.
interestingly mastodon shows me the correct emoji when i use the default web interface.
and according to the Firefox developer tools the emoji comes correctly from the API.
I see it now.
The developer tools of GNOME Web show it wrong,too but if I copy it into Gedit,it works.
And if I copy the rainbow flag from Emojipedia into the twemoji.parse() function,it has the same bug as with the Mastodon response.
That's really weird especially because the native emoji parsers of both my computer with GNOME Web and my tablet with Firefox have the same bug as Halcyon with Twemoji.
So that means the bug is really on the Halcyon side or more likely on the Twemoji side but it's really hard to fix because actually very few programs seem to support it correctly.
In the emojipicker it started working with system emojis when I specified all emoji fonts in CSS as font-family but I don't know how that could help me with Twemoji.
And removing Twemoji isn't an option as very many devices don't have native emoji support or at least no full support.
I'll try some more ways to get it working correctly but I think the chances aren't that good.
I see it now.
The developer tools of GNOME Web show it wrong,too but if I copy it into Gedit,it works.
And if I copy the rainbow flag from Emojipedia into the twemoji.parse() function,it has the same bug as with the Mastodon response.
That's really weird especially because the native emoji parsers of both my computer with GNOME Web and my tablet with Firefox have the same bug as Halcyon with Twemoji.
So that means the bug is really on the Halcyon side or more likely on the Twemoji side but it's really hard to fix because actually very few programs seem to support it correctly.
In the emojipicker it started working with system emojis when I specified all emoji fonts in CSS as font-family but I don't know how that could help me with Twemoji.
And removing Twemoji isn't an option as very many devices don't have native emoji support or at least no full support.
I'll try some more ways to get it working correctly but I think the chances aren't that good.
SORRY,I made a very very big mistake!
Everything works fine with the next update,I promise!
While I still wonder why it's wrong with native system emojis in so many clients and browsers,I could at least fix the Twemoji thing.
My first try to fix it was simply upgrading Twemoji to 11.0,the latest version.
The problem with newer Twemoji versions is that all updated stuff is in the /2/ folder while the / folder is outdated.
Guess what?
I used the / folder so my library update didn't have any effect.
After adding the /2/ it works great even in GNOME Web where native emojis have some problems.
SORRY,I made a very very big mistake!
Everything works fine with the next update,I promise!
While I still wonder why it's wrong with native system emojis in so many clients and browsers,I could at least fix the Twemoji thing.
My first try to fix it was simply upgrading Twemoji to 11.0,the latest version.
The problem with newer Twemoji versions is that all updated stuff is in the /2/ folder while the / folder is outdated.
Guess what?
I used the / folder so my library update didn't have any effect.
After adding the /2/ it works great even in GNOME Web where native emojis have some problems.
Niklas Poslovski
i am still having some issues with emoji rendering. first i thought it might be a problem with my system fonts on my Linux Machine but it also happens on macOS.
https://emojipedia.org/flag-for-european-union/ and https://emojipedia.org/rainbow-flag/ for example are displayed as 2 symbols. (see attached screenshots)
tested on Chrome and Firefox on Linux and on Safari on macOS
I don't think that I can do anything about it as that seems to be an Mastodon related problem. For me it does only work in Mastodon FE. When using Pleroma FE,Pinafore or Brutaldon I get exactly the same bug. They do all use the native system emoji,Halcyon uses the Twemoji library and Mastodon uses Twemoji icons but an own code for rendering them. First I thought it may be an Twemoji bug but it supports combined emojis (multiple unicode chars for one emoji) if the code is correct. In the Mastodon API response the code seems to be wrong so that all but their own emoji parser think that this are two different emojis.
interestingly mastodon shows me the correct emoji when i use the default web interface.
and according to the Firefox developer tools the emoji comes correctly from the API.
I see it now. The developer tools of GNOME Web show it wrong,too but if I copy it into Gedit,it works. And if I copy the rainbow flag from Emojipedia into the twemoji.parse() function,it has the same bug as with the Mastodon response. That's really weird especially because the native emoji parsers of both my computer with GNOME Web and my tablet with Firefox have the same bug as Halcyon with Twemoji. So that means the bug is really on the Halcyon side or more likely on the Twemoji side but it's really hard to fix because actually very few programs seem to support it correctly. In the emojipicker it started working with system emojis when I specified all emoji fonts in CSS as font-family but I don't know how that could help me with Twemoji. And removing Twemoji isn't an option as very many devices don't have native emoji support or at least no full support. I'll try some more ways to get it working correctly but I think the chances aren't that good.
SORRY,I made a very very big mistake! Everything works fine with the next update,I promise! While I still wonder why it's wrong with native system emojis in so many clients and browsers,I could at least fix the Twemoji thing. My first try to fix it was simply upgrading Twemoji to 11.0,the latest version. The problem with newer Twemoji versions is that all updated stuff is in the /2/ folder while the / folder is outdated. Guess what? I used the / folder so my library update didn't have any effect. After adding the /2/ it works great even in GNOME Web where native emojis have some problems.
:D
i was already starting to blame Unicode :P