Telugu has one more glyph (Hallu) names k_ssa (క్ష) which is also part of Unicode list of Telugu Characters. Currently it’s displaying ష when we typed k_ssa while adding glyphs. Please look into it. I’m currently using FontForge. When I tried to test the features of Glyphs App when I heard about it online, I found this problem. Please look into it. If there are any other problems I found meanwhile I’ll report them here.
That letter is not in Unicode 16 nor is it in their roadmap for future versions.
Google’s Noto Sans Telugu font does contain it as an unencoded letter.
Telugu isn’t supported in Glyphs yet. Please read this thread:
What do you mean that it is missing? k_ssa is a conjunct and thous has no unicode. For a lot Indic languages, we provide a glyph set (you can find them in the sidebar in Font View). For Telugu it is missing. We depend on people familiar with the language to help us. Would you be willing to do this?
1 Like
I started to build the sidebar data. If you edit the file as you see fit (mostly adding all conjuncts that are usually needed). But as I see it, the k_ssa might not even be needed as a precomposed glyph as it can be build from ka+ ssa.below (and relying on mark positioning).
the file contains “halfforms” of all consonants, but it might be better to use “below” variants like it is done for Oriya.
sidebarTelugu.plist (3.0 KB)
Thank you for your quick response. I’m willing to make you familiar with Telugu.
Unlike other Indic Fonts (Indian Languages) Telugu has much more complex combinations. Though there’s no Unicode value for క్ష it has all the Guninthas similar to other Hallu characters. క్షా క్షి క్షీ క్షుక్షూ etc., Also half form for క్ష. I can share a font I designed earlier if you want to understand the combinations.
That would be really helpful.
How do i share font?
You can send me a direct message with a link to the font. Or send it by email to support at this domain.
Thanks for the file.
As far as I can see, there are a lot combinations that are not really needed (at least I don’t see a reason).
E.g. ttha_uuMatra: The shape of the uuMatra is a bit different, but I don’t see a reason why. The ttha uuMatra should be set up that when you just type them next to each other, they should look the same as the combined glyph.
I’m not saying that everything needs to be build from components. But great care has to be taken to use components as much as possible.
You should understand the language and local needs to know why those are created specifically like that. Combinations are needed. Otherwise when text is running in paragraphs some glyphs which form a character are split into two lines which are not appropriate. Also when we apply manual kerning characters (guninthas) formed using two gyphs will look odd. Also some combinations like ష్ట్ల will look odd.
I don’t think that is the case. Indic scripts handle clusters as one character, if they made from one precomposed glyph or by mark positioning.
How should it look like and how is it different if you have a precomposed “క్ష” or not?