My experiences with the medical establishment in general have been questionable.

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.

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.

As for why I brought up the 3DO: It's because the TTF2PNG version is just the right size (1MiB, thanks to the 3DO's precedent) to be a retro Unicode font ROM in various old computers and devices. I've even thought about making a version of FreeDOS modeled after DOS/V (a version of MS-DOS made to display Japanese and Korean characters on VGA DOS machines) using it, and I call it "DOS/U" (Unicode DOS). I've also planned on using it in an open-source fantasy retro computer I make as the video chip's internal font, and the audio chip is something else I have planned out too.

I did do the Markdown image embed into the README, as well as a repo link and image in the body of the post, but regrettably Lemmy isn't making the actual post image work.

It's ALL the characters of the font laid out in their Unicode positions in 16x16 cells from U+0000 to U+10FFFF

Actually, technically speaking, that PNG is a preview image. It's ALL the characters of the font laid out in their Unicode positions in 16x16 cells from U+0000 to U+10FFFF

Also I was asleep when ChaoticNeutralCzech replied, and I was really tired when I said I didn't make a preview image. I actually DID, but it's the TTF2PNG build of the font that was generated in a special way that makes it so that the image can be read sequentially from U+0000 to U+10FFFF in 16x16 cells to get the character you want, with no need for a definition file that shows where a codepoint is in the image. Also, it means that it also serves as a 1:1 preview that is properly mapped too.

As for why the image is "black", it has to do with the fact that to store U+0000 to U+10FFFF in 16x16 cells in a way compatible with sequential reading it requires that the sheet be 4096x65536. Blink engine browsers as well as Samsung's Gallery app have no problems viewing it (as well as some others), but there are also quite a few viewers that really hate this size. Oh, and the PNG is in 1bpp Indexed Color mode to get it small enough to fit in the 1MiB figure used by the 3DO console's font chip size (Apparently the 3DO had the largest font chip.) Basically, the TTF2PNG build is its own preview image, but it may be difficult to display on some viewers. Sorry for any confusion.

Please don't hate me.

Here is some documentation of the program's format: http://justsolve.archiveteam.org/wiki/BWTC32Key

Also, it ended up on WikiData (essentially a subsidiary of Wikipedia): https://www.wikidata.org/wiki/Q105859280

Also, the program is FOSS. It's an open standard.

I'm a nonbinary techie who has a certificate in cybersecurity, HTML, and CSS, and an Associate's Degree in networking (and is still in college going for another IT bachelor's degree), and I've been doing technology projects for over a decade. I'm also in the video game modding community, and I also make virtual instruments, electronic music, and do digital art (including 3D printed art, which I've been doing since I was 11. I'm 21 now.) My career goal is to be a technical writer. I've used Linux for 10 years, and I've known how to work a VM since 2011. I've also dabbled in typography and animation. I put effort into my projects, often spending years on them. I even have made plans and libre blobs for ASICs I want to get manufactured. I consider myself a techie of all trades.