What if GS Unicode wasn't just made of pixels?  What if it had a better, more appealing width/height ratio?  What if it utilized the new FS inventory?  And what if I wasn't way too ambitious/crazy in making this?  No idea, but I'm eager to find out!

I've split this font series up by plane (though as of yet only the fonts for Plane 0 and F exist), since .ttf files have a technical limit of 65,535 glyphs.

Things that are planned but not implemented yet are listed as [TBA] (to be added).

This font (Plane 0) should also serve as the hub for most major updates (like those relating to the series as a whole).

Links to planes:

Plane 0: [THIS FONT]
Plane 1: [TBA]
Plane 2: [TBA]
Plane 3: [TBA]
Plane E: [TBA]
Plane F: here
Plane 10: [TBA]

PUA assignments:

E000~E07F - Tengwar
E080~E0FF - Cirth
E100~E62F - <unassigned>
E630~E64F - Seussian Latin Extensions
E650~E88F - <unassigned>
E890~E8DF - Aurebesh
E8E0~EB9F - <unassigned>
EBA0~EBDF - Cistercian Numerals
EBE0~EFFF - <unassigned>
F000~F2FF - Latin Orthographic Extensions
F300~F7BF - <unassigned>
F7C0~F7FF - Kana Orthographic Extensions [TBA]
F800~F8CF - <unassigned>
F8D0~F8FF - Klingon

Additional PUA assignments in supplemental planes, which will be put in their respective fonts:

F0000~F1FAF - <unassigned>
F1FB0~F1FFF - Muric [TBA]
F2000~F235F - canIPA [TBA]
F2360~10FFFF - <unassigned>

Blocks listed [TBA] are subject to change in length and location, while those that aren't are (theoretically) stabilized à la UTC policies.

Feel free to recommend PUA assignments!

Also, it's more than likely I won't know every script well enough that there won't be any mistakes.  If/when I make a mistake, please tell me and I'll do my best to fix it!

Finished! (Took me 3 days)

Private use characters are encoded in Variation Selectors and Latin Ext. D.

(Inspied by The TI-92 Font)