it seemed more gender inclusive.

Quite. It would be even better to be age-inclusive; not all Perl hackers are adults. I've had a quick look and could not find a generic person/human emoji which was not age specific. Perhaps we could just go with 😎 for the hacker person instead?

I believe we're running into the same sort of issue we had with GINGER ROOT — see fairly long discussion starting at "Re^6: Larger profile pic than 80KB?" — namely Microsoft is supplying you (using Win11) with a more recent version of the Segoe UI Emoji font than it supplies me (using Win10).

What I see in your JAPH suggestion is these four glyphs in a line:
⚖️ U+2696 SCALES
🦪 U+1F9AA OYSTER
🧑 U+1F9D1 ADULT
💻 U+1F4BB PERSONAL COMPUTER

I suspect you're seeing just three glyphs: ⚖️ & 🦪, followed by one that looks similar to 👨‍💻 (please confirm).

Looking at your post more closely, I can individually select (with mouse) ⚖️ & 🦪 but I can only select 🧑💻 as a single entity. This is in line with the first paragraph of "Recommended Emoji ZWJ Sequences, v15.1":

"The following are the recommended emoji zwj sequences, which use a U+200D ZERO WIDTH JOINER (ZWJ) to join the characters into a single glyph if available. When not available, the ZWJ characters are ignored and a fallback sequence of separate emoji is displayed. Thus an emoji zwj sequence should only be supported where the fallback sequence would also make sense to a viewer."

I already knew about the ZWJ sequence 👨‍💻 and just posted its components. Had I wrapped them in several <big> tags, I no doubt would have noticed the difference between 🧑 and 👨.

I agree that using ADULT instead of MAN is a better choice; although, of course, you do need a sufficiently recent font to display the ZWJ sequence.

I believe we're running into the same sort of issue we had with GINGER ROOT

Agreed.

I suspect you're seeing just three glyphs: ⚖️ & 🦪, followed by one that looks similar to 👨‍💻 (please confirm).

Confirmed.

Had I wrapped them in several "big" tags, I no doubt would have noticed the difference

Agreed. MAN and ADULT look very similar on my PC! I need to magnify the window to notice any difference. :)

For cheap thrills, just like last time, I've taken Perl and the Browser out of the equation by running the following commands in both a PowerShell window on Windows 11 and a bash window on Ubuntu 22.04.1.

PowerShell on Windows 11:

PS C:\> $joiner = [char]::ConvertFromUtf32(0x200D)
PS C:\> $pc     = [char]::ConvertFromUtf32(0x1F4BB)
PS C:\> $man    = [char]::ConvertFromUtf32(0x1F468)
PS C:\> $person = [char]::ConvertFromUtf32(0x1F9D1)
[download]

PS C:\> "$man"
👨
PS C:\> "$person"
🧑
PS C:\> "$person$joiner$pc"
🧑‍💻
PS C:\> "$man$joiner$pc"
👨‍💻
PS C:\>

bash on Ubuntu:

$ echo -e '\U1F468'
👨
$ echo -e '\U1F9D1'
🧑
$ echo -e '\U1F468\U200D\U1F4BB'
👨‍💻
$ echo -e '\U1F9D1\U200D\U1F4BB'
🧑‍💻

See Also

• uparse - Parse Unicode strings by kcott (2023) - handy tool to see underlying Unicode characters in an emoji
• Re: uparse - Parse Unicode strings by Tux (2023) - ditto
• Re: uparse - Parse Unicode strings by ikegami (2023) - ditto, see unichars and uniprops from Unicode::Tussle

Updated: added See Also section.

👁️🍾👍🦟

I updated Win10 on Friday. cmd.exe starts:

Microsoft Windows [Version 10.0.19045.3636]
(c) Microsoft Corporation. All rights reserved.

C:\Users\ken>
[download]

Your PowerShell commands:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\Users\ken> $joiner = [char]::ConvertFromUtf32(0x200D)
PS C:\Users\ken> $pc     = [char]::ConvertFromUtf32(0x1F4BB)
PS C:\Users\ken> $man    = [char]::ConvertFromUtf32(0x1F468)
PS C:\Users\ken> $person = [char]::ConvertFromUtf32(0x1F9D1)
[download]

PS C:\Users\ken> "$man"
👨
PS C:\Users\ken> "$person"
🧑
PS C:\Users\ken> "$person$joiner$pc"
🧑‍💻
PS C:\Users\ken> "$man$joiner$pc"
👨‍💻
PS C:\Users\ken>

Except in the PowerShell window, all of those glyphs just appear as a square with a question mark inside. So, it would appear that the character information is kept: not rendered in the CLI but is rendered in the browser.

I also updated Cygwin on Friday.

$ uname -a
CYGWIN_NT-10.0-19045 titan 3.4.9-1.x86_64 2023-09-06 11:19 UTC x86_64 
+Cygwin
[download]

Your bash commands:

$ echo -e '\U1F468'
👨

$ echo -e '\U1F9D1'
🧑

$ echo -e '\U1F468\U200D\U1F4BB'
👨‍💻

$ echo -e '\U1F9D1\U200D\U1F4BB'
🧑‍💻

Except in the CLI (/usr/bin/mintty) all glyphs just appeared in their text forms. Also, the ZWJ sequence above, appeared as two separate glyphs: MAN + PC.

— Ken