GS Unicode 3.0 - Plane 0
-
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 GS Unicode 2.0 was actually completed?...
I've split this font series up by plane since font files have a technical limit of 65,535 glyphs.
Things that are planned but not (fully) implemented yet are italicized.
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
Plane 2
Plane 3
(No Unicode characters exist in Planes 4 through D as of U17.0)
Plane E
Plane F
Plane 10PUA assignments:
These should largely conform to the (Under-)ConScript Unicode Registry, found here.
E000~E07F - Tengwar
E080~E0FF - Cirth
E100~E14F - Engsvanyali [Engsvanyáli]
E150~E1AF - Kinya
E1B0~E1CF - Ilianore
E1D0~E1FF - Syai
E200~E26F - Verdurian
E270~E28F - aUI
E290~E2BF - Amman-Iar
E2C0~E2CF - Streich
E2D0~E2FF - Xaini [Xaîni]
E300~E33F - Mizarian
E340~E35F - Zirinka [Zírí:nka]
E360~E37F - Sarkai
E380~E3AF - Thelwik
E3B0~E3FF - Olaetyan
E400~E42F - Niskloz [Nísklôz]
E430~E44F - Kazat Akkorou [Kazat ?Akkorou]
E450~E46F - Kazvarad
E470~E48F - Zarkhand [Zarkhánd]
E490~E4BF - Rozhxh [Røzhxh]
E4C0~E4EF - Serivelna
E4F0~E4FF - Kelwathi
E500~E51F - Saklor
E520~E54F - Rynnan
E550~E57F - Alzetjan
E580~E59F - Telarasso
E5A0~E5BF - Ssuraki [Ssûraki]
E5C0~E5DF - Gargoyle
E5E0~E5FF - Ophidian
E600~E62F - Ferengi
E630~E64F - Seussian Latin Extensions
E650~E67F - Sylabica
E680~E6CF - Ewellic
E6D0~E6EF - Amlin
E6F0~E73F - Unifon Extended-1
E740~E76F - Unifon
E770~E77F - Solresol
E780~E7FF - Visible Speech
E800~E82F - Monofon
E830~E88F - Dni [D'ni]
E890~E8DF - Aurebesh
E8E0~E8FF - Tonal
E900~E97F - Glaitha-A
E980~E9FF - Glaitha-B
EA00~EA9F - Lhenazi
EAA0~EAFF - Wanya
EB00~EB3F - Orokin
EB40~EB5F - Standard Galactic
EB60~EB9F - Braille Extended-1
EBA0~EBDF - Cistercian Numerals
EBE0~EBEF - Lapointe Hexadecimal Numerals
EBF0~EBFF - Martin Hexadecimal Numerals
EC00~EC2F - Cylenian
EC30~EC6F - Syrrin
EC70~ECEF - Graflect
ECF0~ECFF - Whitaker Hexadecimal Numerals
ED00~ED3F - Deini
ED40~ED7F - Niji
ED80~EDAF - Iranic
EDB0~EDDF - Tassarunese
EDE0~EDEF - Zese
EDF0~EDFF - Grawlixes
EE00~EEEF - <UNASSIGNED>
EEF0~EEFF - Font Specifications
F000~F4BF - <UNASSIGNED>
F4C0~F4EF - Ath
F4F0~F89F - <UNASSIGNED>
F8A0~F8CF - Aiha [Aiha (Kesh)]
F8D0~F8FF - KlingonAdditional PUA assignments can be found in the Plane F and 10 fonts.
Feel free to recommend PUA assignments! However, I will probably prioritize natural scripts, then PUA requests from GSU2.0. I will also probably be a bit less likely to add more precomposed characters, as Unicode stopped doing this after U3.0, and I don't want them taking up the entire PUA. If I do add them, they'll be much more organized, and will likely exist entirely in Plane 10.
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!
Special thanks to djnippa who provided a beautiful collection of composite bricks here, which I've used for this font (stored at U+EFFF)!
-
Info:Created on Sun, 15th February. Last edited on Mon, 23rd February.
-
License:
-
Categories:
-
Sets:
-
Tag:
23 Comments
Hello! It's been a while, hasn't it?...
The creation of this font is my first real activity on this site after an almost 2.5-year hiatus, as at this point I believe my mental health and schedule finally permit me to return to fontmaking. I do apologize that I sort of left without much warning, and I further regret to admit that I can't quite confirm I'll be as active as I once was. I hope I can be, but I don't want to make any promises.
However, for now, I present GS Unicode 3.0! This font series will utilize composite bricks provided by djnippa with this font, although I'll be sticking to 1:1, 1:2, 1:3, 2:3, and possibly 1:4 slopes to keep things more organized and less laggy, especially as I approach the 65535-character mark. This will otherwise largely be a continuation of GS Unicode 2.0, meaning it will keep the same width:height ratio, general shapes, and overall "feel" (hopefully). The decision to make an entirely new font, as opposed to continuing work on the former, was one I'd been wrestling over for the past few months as I contemplated my return. Ultimately, two major factors influenced my decision.
Firstly, for reasons I won't go into, I wanted a fresh start to my life, and GS Unicode 2.0 was unfortunately a casualty of a past that I otherwise don't want to remember.
Secondly, and more significantly, I wasn't overall happy with the development path that GS Unicode 2.0 was taking. As the character count mounted, I discovered that the list of things I wanted to change was increasing too, and it was becoming extremely difficult to change a glyph without it affecting others whose geometries were based on it. I've also wanted to restructure the extremely bloated and largely disorganized Private Use Area for quite a while, which was a similarly daunting task. Please know that this is not a criticism of the recommendations y'all have given me. I thoroughly enjoyed all of your creative and imaginative suggestions, and it was actually one of the things I enjoyed most about fontmaking! However, I don't think it's controversial to suggest that there doesn't need to be a 4096-character space filled with just precomposed Latin-diacritic combinations (there's a reason Unicode stopped doing this after U3.0).
If you made a PUA recommendation on GS Unicode 2.0, I'll get to it here in due time, once I'm more organized and this font is more stable. You don't need to re-recommend anything here, as I still have access to the GS Unicode 2.0 page and most of the code charts that I've been sent.
Even though, like its predecessors, GS Unicode 3.0 is meant to be a pan-Unicode font, I've only published it with Basic Latin to see what y'all think of it first. I'm not super happy with some of the curves and angles, especially on 6, 7, 9, &, #, `, and W, so nothing is set in stone yet.
In the meantime though, I'm happy to be back!
i think unicode 17 added characters around plane 9...
Seems odd that Unicode would randomly add characters in Plane 9. Are you sure it's not a fan extension or something? I can't seem to find any info...
Welcome back, Greenstar967.
Anyways, good luck again.
By the way, I'm also working on a Pan-Unicode font project (unicode CTCG).
@Greenstar967 nvm was a mandela effect
reminds me of fairfax HD! lol
I actually did notice that (especially the curves on bdpq)! Totally wasn't intentional though lol
I think, I would not try to draw glyphs, which I am not familiar with, from some unknown scripts, until I would be 100% satisfied with glyphs I know (basic latin).
For me here the 7, Z, z, /and \ would be bare minimum to be solved properly, before moving further. Even if it is intended to be of fixed width, does not mean all glyphs have to fill the whole box, if none of common slopes fills it seamlessly.
I agree. I've so far been unable to find an adequate simple slope without changing the width:height ratio (the closest I've been able to find mathematically is 16:23, which incidentally is the ratio of an A4 sheet of paper). I'm not really fond of either using such a complicated slope or changing the width:height ratio, as I still (for now) want to keep GSU 3 compatible with GSU2. But I'll keep looking, as the / shape is a pretty critical slope. The other concern is that I'd have to find a way to fix / without damaging any of the other slopes....
Use nudging to correct the slopes in NZz07/#\%. My fonts Monospac and NPS Round use nudging to achieve centered slopes; feel free to use them for inspiration.
NZz07/#\% have been fixed. W<>^ have also been altered. Q&~*` are next on the list, as well as perhaps touching up some of the nudged bricks, because I'm not sure I've done them as efficiently as I could've. Thank you Peter (Petruuccio) and erictom333 for the advice though! They definitely look a lot cleaner now.
I wonder if smoothing out the curves using an external font editor is in the plans (if it gets too big to work with in FontStruct)?
Are you going to add Latin-1 Supplement?
@BWM I may end up having to go that route, though I'm not sure yet. Is there one in particular you'd recommend?
@ctcg_ I will add Latin-1 Supplement, as I plan to make this a pan-Unicode font, but I'd like to make sure I'm happy with all of the basic Latin glyphs before I move onto anything more complicated.
For free and open-source font editing software, I use FontForge. It runs on Windows, Mac, and also on Linux.
But if you have the money, then I recommend either Glyphs ($299) or if you don't have a Mac, FontCreator ($49 for Home, $149 for Standard, and $199 for Professional)
add argam numerals and initial teaching alphabet glyphs
@18man The Initial Teaching Alphabet glyphs will be added to Latin Extended-G in September, when Unicode 18 releases.
Why do you publis this with only Basic Latin?
@Greenstar967 Why do you publish this with only Basic Latin?
@erictom333 Why do you no longer update Pixel Sans?
@BWM Why do you no longer update Kemig?
Can you make arabic and hangul
Regarding the PUA encodings, I'm going to revamp SPUCE, shifting around and removing some blocks. Many of the blocks reserved for other users will be removed unless those users oppose. I'm open for suggestions; anything in the (U)CSUR (save for Unifon, which will be encoded as part of the Latin extensions) will be kept.
The SPUCE wiki has been moved to a new wiki on Miraheze; the existing wiki is now deprecated and will no longer be maintained. Most content will be copied over, but some blocks and characters will be relocated or removed.
Please sign in to comment.