Friday, October 17, 2014

Next week Diwali festival in India

Its Diwali festival next week in India.

If you feel you are not getting reply for emails from someone from India or not update on bugzilla from package maintainer just be patient. Its diwali time :)

If one dont know regarding festival read AT http://en.wikipedia.org/wiki/Diwali

Most of the offices used to have back-to-back holidays during this.

I will be working till Monday 20th and then will be away for a week.

Monday, October 13, 2014

Fedora 21 Beta freeze today !!

Fedora 21 Beta freeze today, so if any build pending from you do build it quickly. Not only that ping and ask for quick testing and karma.

I done with 3 important build yesterday from my side.

1. Lohit Assamese: Default font for Assamese language. Pushed latest upsteam release.
2. Lohit Bengali: Default font for Bengali language. Pushed latest upstream release.
3. Lohit Tamil: Default font for Tamil fonts. Pushed latest upstream release.

Pending stuff from me is liberation fonts. I have fixed number of Fedora bugs in ustream and release is pending from me. Once i will do with upstream release will build it first for rawhide and then for Fedora 21.

Release of Lohit Assamese 2.91.0 just after Lohit Bengali 2.91.0

Very natural move. Assamese and Bengali fonts are not much different just 09F0 (ৰ) &  09F1 (ৱ) are extra in Assamese.

Frankly there is no need to create different fonts for these languages. Since we can have OT rules written for 09F0 (ৰ) &  09F1 in same fonts. Bengali user never type these characters and when assamese user will type these character he can get expected rendering.

But Assamese and Bengali communities has strong opinion regarding font  names. Why should Assamese user use Bengali language fonts?

Even recently Assamese communities convinced Unicode to have "Assamese and Bengali" name to Unicode chart rather than only Bengali. There point was there is nothing like Bengali script in Assamese. Do update if i am missing something.

Lohit project respect user communities and will keep Assamese fonts separate. I can remove characters not used in Assamese from Bengali fonts and viceversa for Bengali but its very minor and i dont want one to install other font specifically for two characters.

One more reason to do this release quickly after Lohit Bengali is to make sure we can get testing from wider community.

Other release specific detail is available lohit archive email
 

Friday, October 10, 2014

Fedora has the latest google-noto-fonts with addition of 44 new font families

Last week i done with packaging latest upstream release of Google's ambitious project Noto fonts  (google-noto-fonts).

Last time we packaged it on Aug 2013 with 69 subpackage. With this latest package Fedora 21 has got all the improvements done in upstream over the year.

New package google-noto-fonts has 106 packages. 44 New packages over the earlier release from Google.

I am planning to write one article in FedoraMagzine for it, mentioning how tricky it was to package it for Fedora and what are benefits Fedora gets by packaging noto fonts. What are the missing things in Noto fonts. Stay tuned !!

Bodhi link here

Thursday, October 09, 2014

Lohit Bengali alpha version 2.91.0 is released under Lohit2 project


Was expecting to release Lohit Bengali around June 2014 but it took more time due to priorities of some other work including glibc.

Finally work with Shilpa last couple of week last week and completed this milestone. :)

Lohit Bengali 2.91.0 has number of improvements over earlier release.

TTF size is reduced from 140K to 128K (still some improvement possible by removing halant form which can easily formed by GPOS )

Standard compliance is one more thing happened with this release. Unicode, OpenType spec. If we are still missing something do point us to particular document.

Looking forward for more testing and more improvement in Bengali.

Do read lohit-devel email for more information.

Thursday, September 18, 2014

Lohit Tami 2.91.0 now available for testing

Done with the release of Lohit Tamil 2.91.0 with the improvements planned under Lohit2 project.

Following are highlights:
  1. Rewritten all Open type tables with supporting taml and tml2 tags.
  2. Renamed all the glyphs by following AGL syntax.
  3. Open type tables are available in .fea file and this time it is compiled with AFDKO.
  4. Reusing glyphs by "COPY REFERENCE"
  5. Added GRID FITTING table and auto-hinting by fontforge. (Need to use ttfautohint but we need Latin support to do that)
  6. Tested with Harfbuzz NG and Uniscribe (W8)  (Need to test on WinXp yet)
  7. Auto test module available with test files. (Please help me to add more test cases.)

This release now support characters required for minority orthographies. For more details visit bugzilla

Stopped using deprecated ligature for SRII. See bugzilla for more information.

Wednesday, September 17, 2014

Compiling Lohit fonts feature file with Adobe Font Development Kit

This first came to notice with issue "OTM error #13". Everything was working perfectly with fontforge, creating feature file and importing feature file back :)

But certainly above issue open up number of issues with this process. Font designers were not able to import .fea file due to this issue.

Thanks to Dave and Frank for pointing to issue and directing me towards Adobe Font Development Kit (AFDKO). Adobe is the one created specification for .fea file and provided nice tools to compile it.  Most of the information already available AT http://www.adobe.com/devnet/opentype/afdko/topic_overview.html 

 This blog is specifically to update how i am using AFDKO in Lohit project.

Steps:
1. Write open type tables for Lohit fonts in Fontforge.
2. Export .fea file
3. Generate .ttf by importing .fea file to it using following commands.
4. makeotf -f Lohit-Tamil.ttf -ff Lohit-Tamil.fea

It fails with error but it generates unix Type1 font required for makeotfexe.

What errors :)

  makeotf command pass following arguments to makeotfexe

  "makeotfexe "-f" "Lohit-Tamil.ttf.tmp" "-o" "Lohit-Tamil.ttf.temp_cff" -ff "Lohit-Tamil.fea" -ga -gf "Lohit-Tamil.ttf.temp.GOADB" -mf "FontMenuNameDB" -shw"

In above argument  "-ga -gf "Lohit-Tamil.ttf.temp.GOADB"  are not required but somehow automatically gets added by makeotf.

But makeotf done one good job of converting source font 'Lohit-Tamil.ttf' to temporary Unix Type1 font file 'Lohit-Tamil.ttf.tmp'

5. run makeotfexe removing problem cuasing arguments.
 makeotfexe "-f" "Lohit-Tamil.ttf.tmp" "-o" "Lohit.ttf" -ff "Lohit-Tamil.fea" -mf "FontMenuNameDB" -shw

And here get you Lohit.ttf build by adding .fea file with AFDKO.

Hope so it will help to some others as well.

I specifically found this very useful for finding issues in Lohit-Devanagari.fea files.

Tuesday, September 16, 2014

Lohit Tamil in Unicode charts

This is news to me as well :)

 Just came to know from comment that Lohit Tamil is used in Unicode charts from 7.0 onwards.  I did quick comparison with old Tamil chart and 7.0 and yes that is Lohit !!





Kudos to Shriramana for making this happen with proposal. I remember we were talking about this last year and due to OFL license of Lohit it is easy to use it in Unicode charts without any permission.

This add more responsibility to make sure Lohit Tamil follows and keep glyphs consistent in future version. I am sure with strong community we can achieve it.


 I have been always proposing Unicode for using opensource fonts in there charts. Unicode definitely spending some money to make fonts for these charts, so why not to release these charts under opensource license?


 Presently charts only serve the purpose of reference and even after release of particular version even for single character users need to wait for other fonts to sync with latest Unicode version. If Unicode release latest version of charts with fonts as well, one can just quickly install those fonts. These fonts can be used in all OS due to liberal license, many things can happen...

  Second part that is faced specifically in complex script, is reference for rendering rules. Yeah, this can add additional overhead to Unicode but i strongly feel it can help further to have standardization in complex script rendering.

  Anyway we are already trying for this with Lohit2 project, hopefully  other script fonts project will also start this kind of initiative and in long term font designers will be free from worry of rules for complex script rendering.

  Again glad to see this is happening !!