My experiences with the medical establishment in general have been questionable.
I'm an intersex enby who seeks more androgyny than I have.
The funny thing is that I'm actually intersex, but in a way that only doctors and intimate partners can see. I'm also prone to text walls. The relevant endocrinologist is, to put it simply, behind the times. It's a long story.
UPDATE:
UnifontEX has now received a JSTF table, a process that fixed compatibility with some programs. It also has been given a vector DFONT and a better WOFF1 in terms of bandwith. PLEASE redownload.
Also, what this means is that the doctors never caught that something was amiss, even though it was very visible.
I apologize in advance if this post is potentially able to ruffle some feathers.
I just made a NEC PC-98 version via Neko Project 2 (the Wii version can make TrueType fonts into ANEX86.BMP replacements for PC-98 emulators) which has been uploaded.
It's not that I'm purposefully capping it at 2018. It's that TrueType and OpenType only allow 65535 glyphs, and I'm at 65417. Also, Unifont developers have drawn the relevant glyphs (they've drawn even Unicode 15 Plane 1 and still haven't stopped) but they aren't going to fit, even though they are compatible. I really want to put them in, but the old TrueType/OpenType format is preventing me from doing this. If you want me to put them in, please talk to the OS vendors to utilize Apple's old iOS SVG webfont format which isn't limited to 65535 glyphs. I can't even use versions of Unifont Upper 11 higher than 11.0.01 due to that same 65535 glyph count limit. Also Unifont is not color, and nor is UnifontEX. The trans flag in the retro computer BIOS would be handled by looking for those combining characters and drawing the trans flag in a 16x16 cell using color bars. Oh, and I'm not purposefully capping Upper at 2018. Also, the Tumblr codes aren't in the PUA and either use existing characters or KreativeKorp's Vexillo, which does it via tag characters, which the OS would also look for and fill in in a similar way. Of course, Unifont and UnifontEX's architecture isn't one that handles any sort of joined characters. Any emoji that use ZWJ sequences are always rendered as their components, and this is unfixable. Not to mention that one would run into the 65535 glyph issue pretty much instantly. So, I absolutely agree with your idea, but I unfortunately cannot implement it due to multiple technical limitations. Sorry about that. Also, with regards to the emoji pronouns, the first example that came to mind would be ones like 🐰/🐰s or such.
TL;DR: I absolutely agree with your comment but multiple technical limitations prevent implementation of it.
Also, I'd handle the trans flag sequence in that OS as a one-character (fullwidth) color bar. Also, the environment that would be booted into would be a computing environment, drawn as much as possible in UnifontEX glyphs. A form of super-textmode. But graphics mode would not conflict either. Note that UnifontEX has MANY gender symbols, including ones you would see in the MOGAI community as well as a third flag (U+26FF, the Rumpus Parable agender one). Also, we are dealing with monochrome 16x16 pixel here, so the flags are done in the graphics renderer not the font. I'm literally falling asleep at my keyboard right now and can't think further on this topic, so I will stop here.
The 3DO's BIOS font alone is 1MiB, which is why the file size matters here. UnifontEX-on-a-chip is historically-accurate in terms of file size on 1990s devices (the 3DO Blaster card was literally a 3DO on an ISA card for DOS and DOS/V machines), and in character size (The NEC PC-98, all DOS/V installs, Fujitsu FM Towns, Sharp X68000, and MANY other Japanese computers of the 1980s and 1990s used 16x16 for fullwidth characters and 8x16 for halfwidth characters). So, ignoring the stuff like the Bitcoin symbol, UnifontEX could have existed in an early-1990s console or PC, or upgrade board for a late 1980s machine like the MSX, which had swappable Kanji ROM chips and the needed resolution. Well, rather than just Kanji, how about a decent chunk of Unicode? Also, your comment about late 1990s mobile phones isn't far off. Unicode did exist in the 1990s. Ultimately, UnifontEX's PNG form is historically-accurate given the 3DO's file size. It's why having a 1MiB version is so crucial, because it is within the file size range of Kanji ROMs from the olden days. It's basically a Unicode ROM as well as its own preview image. Think of all the things you can do. You could put it into character LCDs and so many other things. I'm currently tired after a long day of college so I'm not able to go on as long as I usually do.
The join button isn't working.