From psatpute at redhat.com Mon Jan 5 04:19:09 2015 From: psatpute at redhat.com (Pravin Satpute) Date: Mon, 05 Jan 2015 09:49:09 +0530 Subject: [Lohit-devel-list] Lohit2 next releases will be Odia and Telugu Message-ID: <54AA10BD.6030703@redhat.com> Hi All, We had an successful year 2014 for Lohit2 project with following achievements * Automated testing support with the help of hb-shape. * Release of lightest ever Lohit Malayalam font with 25% reduction in characters and 45% reduction in GSUB tables. * Lohit Gurmukhi 2.91.0 (Alpha) release with name change from punjabi to gurmukhi and number of improvements and bug fixes. * Lohit Tamil 2.91.0 (Alpha) release with improvements under lohit2 projects and bug fixes. * Lohit Bengali 2.91.0 (alpha) is now available for testing * Released Lohit Assamese 2.91.0 (Alpha) under lohit2 project In this year first we will try to complete remaining script fonts i.e. Oriya, Telugu and Kannada. We have already started work on Odia and Telugu. Looking forward for release in this month for same. For Odia we had nice discussion with Subhashish Panigrahi and Dr. Nikhil Mohan Pattnaik regarding improvements required in fuelgilt conference. It includes visual as well some rendering rules. We are making sure with new release those will get fix. For Telugu we have started working with Krishnababu Krothapalli, he has provided us test cases. Development is already started in github [1]. Feel free to report any issue or improvement suggestion At [2] Thanks to you all for your help in 2014 for making Lohit2 successful project. Hoping we will do much more in this year. Best Regards, Pravin Satpute 1. https://github.com/pravins/lohit2/ 2. https://github.com/pravins/lohit/issues/new -------------- next part -------------- An HTML attachment was scrubbed... URL: From shilpagite10 at gmail.com Mon Jan 5 08:50:34 2015 From: shilpagite10 at gmail.com (Shilpa Gite) Date: Mon, 5 Jan 2015 14:20:34 +0530 Subject: [Lohit-devel-list] Improvement Plans For Lohit-Telugu Message-ID: Hi All, After the successful improvements in Tamil,Bengali,Assamese and Odia with Lohit2 Project. We now have moved ahead with the improvement plans for Lohit Telugu. Initially we have planned the following things: 1.) Creating a test file for Lohit-Telugu which covers all the combinations. 2.) Renaming the glyphs in a user readable format so that its easily understood. 3.) Rewriting the Open type rules for Lohit-Telugu. 4.) Testing the rules for all combinations. For further reference: https://github.com/pravins/lohit2/ http://www.microsoft.com/typography/OpenTypeDev/telugu/intro.htm http://shilpagite.blogspot.in/2015/01/improvement-plans-for-lohit-telugu.html Regards, Shilpa Gite -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Fri Jan 9 16:24:36 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 09 Jan 2015 16:24:36 +0000 Subject: [Lohit-devel-list] [Bug 648350] Proper Bold for Lohit Devanagari In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=648350 --- Comment #9 from Fedora End Of Life --- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ToDrgMUaD8&a=cc_unsubscribe From bugzilla at redhat.com Fri Jan 9 21:59:27 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 09 Jan 2015 21:59:27 +0000 Subject: [Lohit-devel-list] [Bug 839303] [ta_IN] Submission of glyphs for Tamil fractions/symbols to be included in the Lohit Tamil fonts In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=839303 --- Comment #10 from Fedora End Of Life --- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4TjRtzIFk0&a=cc_unsubscribe From bugzilla at redhat.com Wed Jan 14 09:30:50 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 14 Jan 2015 09:30:50 +0000 Subject: [Lohit-devel-list] [Bug 839303] [ta_IN] Submission of glyphs for Tamil fractions/symbols to be included in the Lohit Tamil fonts In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=839303 Pravin Satpute changed: What |Removed |Added ---------------------------------------------------------------------------- Version|19 |20 --- Comment #11 from Pravin Satpute --- Moving to next Fedora release. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=QEISxJtTDR&a=cc_unsubscribe From bugzilla at redhat.com Wed Jan 14 09:46:03 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 14 Jan 2015 09:46:03 +0000 Subject: [Lohit-devel-list] [Bug 648350] Proper Bold for Lohit Devanagari In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=648350 Pravin Satpute changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |apatil at redhat.com --- Comment #10 from Pravin Satpute --- *** Bug 963648 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=dUy0geg2NQ&a=cc_unsubscribe From bugzilla at redhat.com Wed Jan 14 09:53:37 2015 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 14 Jan 2015 09:53:37 +0000 Subject: [Lohit-devel-list] [Bug 648350] Proper Bold for Lohit Devanagari In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=648350 Pravin Satpute changed: What |Removed |Added ---------------------------------------------------------------------------- Component|freetype |lohit-devanagari-fonts Version|19 |21 Assignee|mkasik at redhat.com |psatpute at redhat.com --- Comment #11 from Pravin Satpute --- While observing i found that whenever we apply some matra (reph, e-matra) it issue happens. It means we might need some fixes from font size. Moving to Lohit. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ogM4UYfVO1&a=cc_unsubscribe From psatpute at redhat.com Thu Jan 22 06:31:01 2015 From: psatpute at redhat.com (Pravin Satpute) Date: Thu, 22 Jan 2015 12:01:01 +0530 Subject: [Lohit-devel-list] Lohit Change proposals for Fedora 22 Message-ID: <54C09925.1070402@redhat.com> Hi all, Lohit is default font for number of Indian language in Fedora. We are presently in active development of Odia and Telugu. Mostly this will get done before Fedora Alpha release and it will be part of Fedora. For better visibility of change and more testing i have proposed Change proposal in Fedora. One can go through it from Change proposal page. [1] Change it self contained and already accepted :) Looking forward for 100% completion of this change. Regards, Pravin Satpute 1. https://fedoraproject.org/wiki/Changes/Lohit2_Odia_Telugu From psatpute at redhat.com Thu Jan 29 08:18:18 2015 From: psatpute at redhat.com (Pravin Satpute) Date: Thu, 29 Jan 2015 13:48:18 +0530 Subject: [Lohit-devel-list] In long term we should use Adobe font development kit (AFDKO) for Lohit ttf build Message-ID: <54C9ECCA.2070404@redhat.com> Hi All, I was thinking for this from some time now. Reasons: 1. Lots of well know fonts are using AFDKO. AFAIK Adobe fonts are build using AFDKO. 2. Things we required in Lohit specifically, easy to read feature files and final ttf with Adobe glyph naming guideline looks easily manageable with AFDKO. (/GlyphOrderAndAliasDB and .Fea/) 3. AFDKO feature file compilation is much better than Fontforge. Noticed this earlier with OTM errors. Also while compiling i found number of error not identified by fontforge. 4. All command line, so we can automate very nicely. 5. We will use fontforge only for outline related work. Presently we are still using fontforge for OpenType rules writing, i have not faced any problem into it yet. But perfect solution is we should write open type rules in .fea file itself. This at least not targeting presently Regards, Pravin Satpute -------------- next part -------------- An HTML attachment was scrubbed... URL: From psatpute at redhat.com Thu Jan 29 10:32:05 2015 From: psatpute at redhat.com (Pravin Satpute) Date: Thu, 29 Jan 2015 16:02:05 +0530 Subject: [Lohit-devel-list] [Announce] Release 2.91.0 (Alpha) version of Lohit Odia Message-ID: <54CA0C25.1040304@redhat.com> Hi All, As indicated earlier with an emails [1] regarding work on Lohit Odia. Glad to announce that we have completed first stage for Lohit Odia. * Following are **important points:* * Followed Unicode specifications. * Re-writing all GSUB rules. * Open type rules are available in .fea file for easy re-usability. * Feature file compiled with AFDKO. * Supports 'orya' and 'ory2' opentype specifications tag. * Developer friendly glyphs names with AGL syntax format. * Corrected glyph class for all glyphs. * Improved shape of ka-viramasignodia-taodia. * Added Glyph positioning rules for below based matras. * Test file available with release tarball. * Auto testing support with harfbuzz hb-shape.Tested with Harfbuzz and Uniscribe (W8 and XP) In next release we have to work on couple of bugs. Still one major things remain is adding Latin support, it might take long time. This is alpha release and definitely going to have few issues. Need your help for testing it. Download links are available at Lohit project [2] page with name lohit-odia*2.91.0. Direct TTF also available on [3]. Feel free to report issues on lohit git [4] I would like to give special thanks Manoj Giri for his help in testing and Shilpa for working on GSUB rewriting task. Thanks, Pravin Satpute 1. https://www.redhat.com/archives/lohit-devel-list/2015-January/msg00000.html 2. https://fedorahosted.org/lohit/ 3. https://pravins.fedorapeople.org/Lohit-Odia.ttf 4. https://github.com/pravins/lohit/issues/new -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at lab6.com Thu Jan 29 14:47:54 2015 From: dave at lab6.com (Dave Crossland) Date: Thu, 29 Jan 2015 09:47:54 -0500 Subject: [Lohit-devel-list] In long term we should use Adobe font development kit (AFDKO) for Lohit ttf build In-Reply-To: <54C9ECCA.2070404@redhat.com> References: <54C9ECCA.2070404@redhat.com> Message-ID: AFDKOs libre version doesn't include the removeOverlap() method, so you need something else to do that, and fontforge improved its version substantially last year. Fontforge also improved its UFO support, such that you can use it to develop UFO+FDK projects (like Adobe Source Sans+Serif) However, Fontforge has supported importing and exporting fea files for many years, and is scriptable for command line use. Before deciding to switch, I recommend setting up both a fontforge and fdk based workflow from the same source and comparing the resulting binaries, and also considering how maintainable and comprehensive each is. On Jan 29, 2015 3:18 AM, "Pravin Satpute" wrote: > Hi All, > > I was thinking for this from some time now. > Reasons: > 1. Lots of well know fonts are using AFDKO. AFAIK Adobe fonts are build > using AFDKO. > 2. Things we required in Lohit specifically, easy to read feature files > and final ttf with Adobe glyph naming guideline looks easily manageable > with AFDKO. (*GlyphOrderAndAliasDB and .Fea*) > 3. AFDKO feature file compilation is much better than Fontforge. Noticed > this earlier with OTM errors. Also while compiling i found number of error > not identified by fontforge. > 4. All command line, so we can automate very nicely. > 5. We will use fontforge only for outline related work. Presently we are > still using fontforge for OpenType rules writing, i have not faced any > problem into it yet. But perfect solution is we should write open type > rules in .fea file itself. This at least not targeting presently > > Regards, > Pravin Satpute > > _______________________________________________ > Lohit-devel-list mailing list > Lohit-devel-list at redhat.com > http://www.redhat.com/mailman/listinfo/lohit-devel-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From psatpute at redhat.com Fri Jan 30 04:14:17 2015 From: psatpute at redhat.com (Pravin Satpute) Date: Fri, 30 Jan 2015 09:44:17 +0530 Subject: [Lohit-devel-list] In long term we should use Adobe font development kit (AFDKO) for Lohit ttf build In-Reply-To: References: <54C9ECCA.2070404@redhat.com> Message-ID: <54CB0519.5070104@redhat.com> On Thursday 29 January 2015 08:17 PM, Dave Crossland wrote: > > AFDKOs libre version doesn't include the removeOverlap() method, so > you need something else to do that, and fontforge improved its version > substantially last year. > > Fontforge also improved its UFO support, such that you can use it to > develop UFO+FDK projects (like Adobe Source Sans+Serif) > > However, Fontforge has supported importing and exporting fea files for > many years, and is scriptable for command line use. > > Before deciding to switch, I recommend setting up both a fontforge and > fdk based workflow from the same source and comparing the resulting > binaries, and also considering how maintainable and comprehensive each > is. > Agree with you. We will do comparison. I am thinking for at least one change is to use makeotf for building ttf. I think OTM and Fontlab using it in the backend. So good if we can build Lohit ttf also with it. Regards, Pravin Satpute > On Jan 29, 2015 3:18 AM, "Pravin Satpute" > wrote: > > Hi All, > > I was thinking for this from some time now. > Reasons: > 1. Lots of well know fonts are using AFDKO. AFAIK Adobe fonts > are build using AFDKO. > 2. Things we required in Lohit specifically, easy to read > feature files and final ttf with Adobe glyph naming guideline > looks easily manageable with AFDKO. (/GlyphOrderAndAliasDB and .Fea/) > 3. AFDKO feature file compilation is much better than Fontforge. > Noticed this earlier with OTM errors. Also while compiling i found > number of error not identified by fontforge. > 4. All command line, so we can automate very nicely. > 5. We will use fontforge only for outline related work. > Presently we are still using fontforge for OpenType rules writing, > i have not faced any problem into it yet. But perfect solution is > we should write open type rules in .fea file itself. This at > least not targeting presently > > Regards, > Pravin Satpute > > _______________________________________________ > Lohit-devel-list mailing list > Lohit-devel-list at redhat.com > http://www.redhat.com/mailman/listinfo/lohit-devel-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at lab6.com Fri Jan 30 04:15:53 2015 From: dave at lab6.com (Dave Crossland) Date: Thu, 29 Jan 2015 23:15:53 -0500 Subject: [Lohit-devel-list] In long term we should use Adobe font development kit (AFDKO) for Lohit ttf build In-Reply-To: <54CB0519.5070104@redhat.com> References: <54C9ECCA.2070404@redhat.com> <54CB0519.5070104@redhat.com> Message-ID: Yes, there are only 3 font compilers, fdk, FontForge, and opentype.js On Jan 29, 2015 11:14 PM, "Pravin Satpute" wrote: > On Thursday 29 January 2015 08:17 PM, Dave Crossland wrote: > > AFDKOs libre version doesn't include the removeOverlap() method, so you > need something else to do that, and fontforge improved its version > substantially last year. > > Fontforge also improved its UFO support, such that you can use it to > develop UFO+FDK projects (like Adobe Source Sans+Serif) > > However, Fontforge has supported importing and exporting fea files for > many years, and is scriptable for command line use. > > Before deciding to switch, I recommend setting up both a fontforge and fdk > based workflow from the same source and comparing the resulting binaries, > and also considering how maintainable and comprehensive each is. > > Agree with you. We will do comparison. > I am thinking for at least one change is to use makeotf for building ttf. > I think OTM and Fontlab using it in the backend. So good if we can build > Lohit ttf also with it. > > Regards, > Pravin Satpute > > > On Jan 29, 2015 3:18 AM, "Pravin Satpute" wrote: > >> Hi All, >> >> I was thinking for this from some time now. >> Reasons: >> 1. Lots of well know fonts are using AFDKO. AFAIK Adobe fonts are build >> using AFDKO. >> 2. Things we required in Lohit specifically, easy to read feature files >> and final ttf with Adobe glyph naming guideline looks easily manageable >> with AFDKO. (*GlyphOrderAndAliasDB and .Fea*) >> 3. AFDKO feature file compilation is much better than Fontforge. >> Noticed this earlier with OTM errors. Also while compiling i found number >> of error not identified by fontforge. >> 4. All command line, so we can automate very nicely. >> 5. We will use fontforge only for outline related work. Presently we >> are still using fontforge for OpenType rules writing, i have not faced any >> problem into it yet. But perfect solution is we should write open type >> rules in .fea file itself. This at least not targeting presently >> >> Regards, >> Pravin Satpute >> >> _______________________________________________ >> Lohit-devel-list mailing list >> Lohit-devel-list at redhat.com >> http://www.redhat.com/mailman/listinfo/lohit-devel-list >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: