tag:blogger.com,1999:blog-6213436528085236698.post6081641778341609217..comments2020-08-26T23:40:32.470-07:00Comments on Sneha Kore: The Way We Proceed With Malayalam ..Sneha Korehttp://www.blogger.com/profile/11816611405404358988noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-6213436528085236698.post-15755664078392390662013-12-29T23:43:06.715-08:002013-12-29T23:43:06.715-08:00Thats nice feature of fontforge considering random...Thats nice feature of fontforge considering random glyph naming behaviors of font developers. We need to work and improve it in longterm. I will try and give feedback on same.Pravin Satputehttps://www.blogger.com/profile/18185428997338500256noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-23454706092017441602013-12-27T05:49:32.928-08:002013-12-27T05:49:32.928-08:00FontForge has an option to rename glyphs at font g...FontForge has an option to rename glyphs at font generation time using a name list, so you can have whatever readable names you like during development and generate AGL-compatible names at build time. I never used that option, though, so no idea how reliable is it, but it is worth considering. In my feature files I always use classes and name them to my liking, so I rarely interact with “raw” glyph names.Khaled Hosnyhttps://www.blogger.com/profile/15326819579528894502noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-36341556403949546102013-12-26T02:24:26.711-08:002013-12-26T02:24:26.711-08:00Thanks Khaled for clirifications.
We had some goo...Thanks Khaled for clirifications.<br /><br />We had some good discussion about AGL on http://sourceforge.net/adobe/aglfn/discussion/discussion/thread/f212153e/<br /><br />1. One of the goal of Lohit2 is to have readable rules in .fea file. uXXXX is not that readable. <br />2. while using aglfn.txt we found it is not updated from long time.<br />3. Right now we are following AGL syntax i.e. <br /> A. "_" in glyph name left part and "." in right side "alt"<br /> B. Ligatures are named with its componants name <br /> fi is name as "f_i"<br /><br />i think Idea proposed by Dave in http://sourceforge.net/adobe/aglfn/discussion/discussion/thread/f212153e/#577e will help to not only Lohit but all fonts following AGL syntax but not names uXXXX.Pravin Satputehttps://www.blogger.com/profile/18185428997338500256noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-522207279956242352013-12-26T01:21:58.463-08:002013-12-26T01:21:58.463-08:00Yes, I mean that.
First, you should be using aglf...Yes, I mean that.<br /><br />First, you should be using aglfn.txt (AGLFN; Adobe Adobe Glyph List For New Fonts) as glyphlist.txt is the legacy glyph list that should not be used for new fonts.<br /><br />The algorithm used to reverse map glyph names to Unicode characters is described here http://sourceforge.net/adobe/aglfn/wiki/AGL%20Specification/, and since it is the sole purpose of using AGL, glyph names should follow it. From the spec the glyph name “kamlm_viramamlm_ssamlm” is wrong since neither AGLFN nor AGL has glyphs with the names “kamlm”, “viramamlm” or “ssamlm”, so here names should be constructed from the Unicode values, namely “uni0D15”, “uni0D4D” and “uni0D37”, and the ligature can be named “uni0D15_uni0D4D_uni0D37” or the shorter (but a bit less readable) “uni0D150D4D0D37”.Khaled Hosnyhttps://www.blogger.com/profile/15326819579528894502noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-71046738795558406522013-12-22T22:53:13.889-08:002013-12-22T22:53:13.889-08:00khaled do you means to follow ALG glyphlist.txt (h...khaled do you means to follow ALG glyphlist.txt (http://kaz.dl.sourceforge.net/project/aglfn.adobe/glyphlist.txt)? little bit elaboration will help on AGL voilation part :)Pravin Satputehttps://www.blogger.com/profile/18185428997338500256noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-31966370423281074592013-12-22T12:26:11.754-08:002013-12-22T12:26:11.754-08:00This seems to be an OpenType/Adobe limitation that...This seems to be an OpenType/Adobe limitation that FontForge enforces http://partners.adobe.com/public/developer/opentype/index_glyph2.html#4. But I’m confused since you said you are following the AGL, but those names in your example do not follow AGL.Khaled Hosnyhttps://www.blogger.com/profile/15326819579528894502noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-11727090712647902182013-12-18T03:02:22.647-08:002013-12-18T03:02:22.647-08:00Hi Khaled,
Thankx for the feedback. For Gly...Hi Khaled,<br /> Thankx for the feedback. For Glyph-naming style presently we have followed : <br /> <br />>> glyph_components + LANG_tag<br /><br />e.g. unicode value U+0D15 --> kamlm <br /><br />for conjuncts, the glyph components has been seperated by "_".<br /><br />>> component1_component2_component3<br /><br />e.g (U+0D15) ka +(U+0D4D) virama + (0D37) ssa i.e. { ക്ഷ } --> renamed as kamlm_viramamlm_ssamlm<br /><br />But the next thing that we came across was, there were some glyphs which were exceeding the length above 31 characters. so that was limited by fontforge application as it has 31 character exceeding limit.<br /><br />say for e.g. sa_virama_ta_virama_ra {സ്ത്ര } (0D38+0D4D+0D24+0D4D+0D30)<br /><br />for this case, if we followed the above syntax, it is exceeding 31 character limit. so for such cases we have removed "mlm" tag. If you can come out with solution for this issue, that is always appreciated . Sneha Korehttps://www.blogger.com/profile/11816611405404358988noreply@blogger.comtag:blogger.com,1999:blog-6213436528085236698.post-84466239252033959322013-12-16T03:32:43.634-08:002013-12-16T03:32:43.634-08:00I’m interested about the lengthy glyphnames issue ...I’m interested about the lengthy glyphnames issue in FontForge, can you elaborate?Khaled Hosnyhttps://www.blogger.com/profile/15326819579528894502noreply@blogger.com