could you add arabic, devanagari, thai, ethiopic, runic, ucas, cherokee, old turkic, lycian, lydian, carian, palmyrene, nabetean (and also the combining marks)
EDIT: Implemented into the font with version 1.016. ⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻ Unfortunately, I am not able to do certain scripts because they are too complex for me to make in FontForge or requires combining characters. The scripts you mentioned that falls under this are Arabic, Devanagari, and Thai. For the combining marks, those are too difficult for me to get working correctly. For the rest of the scripts you mentioned, I have taken a good look at each of these, and they appear to be doable (minus the three combining characters in Ethiopic), although some glyphs may have complex shapes, so could take time to prefect. This may take a while to implement due to the sheer number of characters…
could you make this font variable?
FontForge currently does not have that kind of capability from its native menus. While I can open said fonts, I cannot generate one from FontForge: https://github.com/fontforge/fontforge/issues/2882
should the mark on the glottal a be disappearing out of thin air whenever i activate .ss01?
Thanks for spotting that! It will be fixed in the next version.
this font looks nice. how is it pronounced tho
Thanks! If you mean the name of the font, /kəːˈlæg.mɑː.ti/.
Some VS characters aren't rendering correctly in my browser, and some other software. What gives? Also, ⟘ and ⟙ are swapped around.
I've looked into the font, and these characters are defined in format14 and GSUB, not all of them will work in certain software. All of them work in LibreOffice Writer; All of them work in Chrome, except for U+267F U+FE00 and U+26F9 U+FE00; For Vegas Pro 19: Only the BMP ones work in Titles and Text, None work in Legacy Text, and all of them work in Protype Titler. With text plugins, support for them varies; and so on. It's not the font's fault, it's the software. I can't really do much regarding the software. As for your other part of the message, thanks for noticing. I've fixed that, and will log it in the version history soon.
Hey. You might want to try using format14 for variant characters to appear correctly on all browsers. (You can do this by opening glyph info, then defining the variants for the variant characters (named uniXXXX/uXXXXX_uniFE0x.ccmp)
Good catch. I noticed font fallback for certain sequences in Chrome. I tried that, and that appears to make it not fallback, but I'll still have them defined in GSUB as well.
Over 12.000 glyphs? I wonder which font editor you've used to do all that? (especially all the OpenType features)
I used FontForge to create this font. It's free, open-source, and runs on Windows, Mac, and Linux. It's not as powerful as the paid alternatives, but it supports creation of OpenType features.
EDIT: Version 1.009 is out, which fixes these issues. Please uninstall any old versions beforehand. ⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻ Hello there! I have found issues with a few characters in the font. These will be fixed when the Unicode 18 characters are added to the font, which will be sometime when the Beta review period comes out. The reason why I'm choosing to wait to fix them is because in the 2025 version of FontForge, font generation is broken and makes files that do not work; and in the 2023 version, there is a bug that can happen if used to generate many font files. If I fixed the issues now, I would need to generate four files, then another four after adding the Unicode 18 characters, for a total of eight files over that period of time. ⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻⸻ Here is a list of the currently problematic glyphs, which styles are affected, and what you can do if you need to use them in your work now: U+1E38: dot below is missing - all styles Fix: Input "Ḷ" in a separate textbox and position it so it is on top of this glyph. U+1E39: dot below is missing - all styles Fix: Input "ḷ" in a separate textbox and position it so it is on top of this glyph. U+02A9: appears as an f+n ligature instead of an f+eng ligature - all styles Fix: Input "ŋ" in a separate textbox and position it so it is on top of this glyph, where the "n" is. U+1DF00: same reason as uni02A9 - all styles Fix: Input "ŋ" in a separate textbox and position it so it is on top of this glyph, where the "n" is. U+10790: same reason as uni02A9 - all styles Fix: Input "ⁿ" in a separate textbox and position it so it is on top of this glyph, where the "n" is.
this looks similar to your lentariso font
While there are some similarities to Lentariso, a vast amount of characters are different. This font supports scripts that not even Lentariso supports. While typing this, I noticed that a few legacy symbols (mainly U+1CC90) weren't at width 1600 when they should be. I hope to push out an update that fixes that, and maybe add a few characters… Before you ask "Why not make all symbols in the SLC blocks width 1600?" Well, the outlined Latin letters could be used to style text, the two airplanes in that block could be used in tandem with the other two, and the diagonal arrows with bars could be used in tandem with the other four. For those reasons, I intentionally made those not at width 1600.
I wonder when you are going to add Unicode 18 characters to this font? It looks so nice! https://www.unicode.org/versions/Unicode18.0.0/
I am choosing to wait for the Beta review period, where the character repertoire is for the most part stable, than to add the characters now and the chance of having to move characters around if any get relocated. Thanks for the compliment though.
This font looks pretty nice. Too bad there aren't any combining marks though. Microsoft and Apple should add this as system fonts.
1) Thanks for the compliment! 2) That's more a limitation of my ability to use mark/mkmk features. 3) I doubt that they would scour sites like these for fonts to include in their OS.
Why are the symbols in the Tibetan blocks the word illegal in front of an X?
While the symbol itself has existed for a while, the symbol is considered illegal and banned from public displays in many countries around the world due to around 12 years of history that occurred in the 20th century. Per United States laws, Atabook's Terms of Service, and Neocities's Terms of Service, this type of topic will NOT be talked about any further.