<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi All,<br>
<br>
I am hoping now most of the contributors around are aware
regarding the lohit2 project. Before the Alpha release of Lohit
Devanagari i think it is important to go through once again goals we
planned for this project[1].<br>
<br>
Goals:<br>
<br>
<b> 1. Cleaning Lohit Open type tables.</b><br>
Highlights are as below<br>
- We rewritten all GSUB rules from scratch.<br>
- New rules are supporting both deva and dev2 script tag<br>
- Done testing on Harfbuzz as well with Uniscribe and its giving
expected results.<br>
- Kept GPOS tables intact.<br>
- Effectiveness and efficiency [2] (sfd file size is down by
28K and Binary file side is down by 4K)<br>
<br>
Found one bug w.r.t harfbuzz [3] and looking forward to get it
resolved soon. Presently it is in know issue list.<br>
<br>
By Beta we will have some more improvement on this.<br>
<br>
<b> 2. Reusable Open type tables.</b><br>
We got two important suggestions on this line, so below are
suggestions and action taken on it.<br>
<b> 1st suggestion</b><br>
To have feature file separate than shapes .sfd file for easy
re-usability of OT rules.<br>
- Thanks to AravindaK, he has already done some work on that
line[4], so just using those stuff. I have forked this gitrepo and
doing some improvement in it. Once done will request Aravinda to
merge with his repo.<br>
<br>
<b> 2nd suggestion</b><br>
To follow AGL[5] and to have readable glyph naming. We were
also thinking from this perspective.<br>
- This has became a bit complex glyphlist.txt [6] suggest
names like "kadeva" or uni0915. But we dont want to follow uni0915
as it is not very readable considering our re-usability goals.<br>
- {0915 (kadeva) + 094D (viramadeva) + 0937 (ssadeva)}
following this create chances of glyph name string more than 31
characters limit.<br>
- So present plan is follow above
"kadeva_viramadeva_ssadeva" as much as possible and if it goes above
31 characters we will discard "deva" part from glyphname.<br>
<br>
<br>
<b> 3. Following of existing standards/guidelines</b><br>
Dont know how many of you aware regarding "Devanagari Script
Behaviour For Hindi"[7] Draft, so its basically guideline for Font
developers. I have one blog pending on this. Though this is draft
mode we are trying to follow this, since it is very informative and
prepared after consulting to language experts.<br>
<br>
This is where we upto, if anything more needed do provide me
your feedback. Also need to decide on release version, i think some
version with -alpha will work.<br>
<br>
Best Regards,<br>
Pravin Satpute<br>
<br>
<br>
<br>
<br>
<br>
1.
<a class="moz-txt-link-freetext" href="http://pravin-s.blogspot.in/2013/08/project-creating-standard-and-reusable.html">http://pravin-s.blogspot.in/2013/08/project-creating-standard-and-reusable.html</a><br>
2. Effective means it should work on all supported platform
perfectly and efficient means compact and clear rule<br>
3. <a class="moz-txt-link-freetext" href="https://bugs.freedesktop.org/show_bug.cgi?id=69266">https://bugs.freedesktop.org/show_bug.cgi?id=69266</a><br>
4. <a class="moz-txt-link-freetext" href="https://github.com/aravindavk/">https://github.com/aravindavk/</a><br>
5. <a class="moz-txt-link-freetext" href="https://sourceforge.net/adobe/aglfn/wiki/AGL%20Specification/">https://sourceforge.net/adobe/aglfn/wiki/AGL%20Specification/</a><br>
6. <a class="moz-txt-link-freetext" href="http://kaz.dl.sourceforge.net/project/aglfn.adobe/glyphlist.txt">http://kaz.dl.sourceforge.net/project/aglfn.adobe/glyphlist.txt</a><br>
7.
<a class="moz-txt-link-freetext" href="http://tdil-dc.in/tdildcTemp/articles/75443Consolidated%20Feedback%20&%20Observations%20on%20Draft%20Devnagari%20Script%20Behaviour%20Ver%201.4.8_June_13.pdf">http://tdil-dc.in/tdildcTemp/articles/75443Consolidated%20Feedback%20&%20Observations%20on%20Draft%20Devnagari%20Script%20Behaviour%20Ver%201.4.8_June_13.pdf</a><br>
</body>
</html>