Re^9: Larger profile pic than 80KB?

[eyepopslikeamosquito]

All of those characters (except GINGER ROOT, as described above) are rendered for me by Firefox. The characters GINGER ROOT and LUNGS are not rendered in my Cygwin CLI; they appear as a question mark inside a square.

Thanks kcott for motivating me to learn a bit more about this topic.

To take Perl and the Web Browser out of the equation, and just test basic platform support, I ran the following simple test on both my Windows 11 laptop and its embedded WSL Ubuntu Linux 22.04.

On Ubuntu, running the following t1.bash script at the shell command prompt:

#!/usr/bin/bash
echo -e '\U1F5A7'     # THREE NETWORKED COMPUTERS
echo -e '\U274E'      # NEGATIVE SQUARED CROSS MARK
echo -e '\U1FADA'     # GINGER ROOT
echo -e '\U1F330'     # CHESTNUT
echo -e '\U1F34E'     # RED APPLE
echo -e '\U1F60B'     # FACE SAVOURING DELICIOUS FOOD
echo -e '\U1F384'     # CHRISTMAS TREE
echo -e '\U1F6F9'     # SKATEBOARD
echo -e '\U1F3D8'     # HOUSE BUILDINGS
echo -e '\U1FAC1'     # LUNGS

resulted in every one of the gang of ten symbols displayed correctly in the shell window.

On Windows 11, running the following PowerShell commands:

[char]::ConvertFromUtf32(0x1F5A7)    # THREE NETWORKED COMPUTERS
[char]::ConvertFromUtf32(0x274E)     # NEGATIVE SQUARED CROSS MARK
[char]::ConvertFromUtf32(0x1FADA)    # GINGER ROOT
[char]::ConvertFromUtf32(0x1F330)    # CHESTNUT
[char]::ConvertFromUtf32(0x1F34E)    # RED APPLE
[char]::ConvertFromUtf32(0x1F60B)    # FACE SAVOURING DELICIOUS FOOD
[char]::ConvertFromUtf32(0x1F384)    # CHRISTMAS TREE
[char]::ConvertFromUtf32(0x1F6F9)    # SKATEBOARD
[char]::ConvertFromUtf32(0x1F3D8)    # HOUSE BUILDINGS
[char]::ConvertFromUtf32(0x1FAC1)    # LUNGS

also resulted in every one of the gang of ten symbols displayed correctly in the Powershell window.

The characters GINGER ROOT and LUNGS are not rendered in my Cygwin CLI

I'm not running Cygwin. However, if you open a Powershell window on your Windows 10 box and type these two commands:

[char]::ConvertFromUtf32(0x1FADA)    # GINGER ROOT
[char]::ConvertFromUtf32(0x1FAC1)    # LUNGS

it would be interesting to see if these two emojis are rendered correctly.

[kcott]

"... if you open a Powershell window on your Windows 10 box and type these two commands: ..."

Did that: both returned a question mark inside a square.

[eyepopslikeamosquito]

Thanks for letting me know.

AFAICT, Win10 is nearing EOL in 2025 ... so it seems unlikely that the not-working rendering of the (critical-to-us) Ginger Root emoji will be deemed critical enough to be fixed by future Microsoft security updates. :)

[kcott]

Your point about Win10 EOL is interesting. I was aware of it; I don't really like what I see in demos of Win11; I'm putting off a decision about that; but that's a rant for another day.

I used to run Mac OS X (which became macOS) for quite a few years. The font it used for emoji was "Apple Color Emoji". In general, I liked the images used for the glyphs. Some seemed a little too detailed for viewing in a normal sized paragraph font; but in the main they were OK.

About 4-5 years ago, I switched to Win10. The font it uses for emoji is "Segoe UI Emoji". Its emoji glyphs were a little less detailed which was good; however, it chose to surround each with a thick, black border which I really didn't like (but put up with it).

I don't know exactly, but the release of Win11 was about the time of Unicode 10 or 11 (I'm guessing here). Unless "Segoe UI Emoji" completely stagnated, I received no further updates for that font. What I have been seeing for newer emoji glyphs is that the thick, black border had disappeared.

This current subthread prompted me to investigate a bit further. What I found was that my browser (Firefox) had been picking up the slack and rendering these newer emoji in its own font, "Twemoji Mozilla".

I keep a number of local HTML pages with notes for myself: TODO lists, HOWTO info, and such like. Just to liven these up a little, over time I've added emoji to the titles (and a few other places); for example, a page with skeleton code has a U+2620 SKULL AND CROSSBONES.

So today, I tweaked the CSS for those pages, putting "Twemoji Mozilla" before "Segoe UI Emoji", and pretty much all of those thick, black borders have disappeared. Yay!

It makes me wonder if Microsoft is not updating "Segoe UI Emoji" for Win10, but is doing it for Win11. Perhaps hoping for: "The new emoji are not rendering on my Win10, but look great on my friend's Win11: I should upgrade now!" — just a thought.