Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tamil Support #16

Closed
8 tasks done
pathumego opened this issue Sep 8, 2015 · 8 comments
Closed
8 tasks done

Tamil Support #16

pathumego opened this issue Sep 8, 2015 · 8 comments

Comments

@pathumego
Copy link
Member

pathumego commented Sep 8, 2015

EDITED

  • Add Tamil sources files
  • Add Tamil feature files/GOADB (@paarandiak)
  • Set glyph names to global structure to match GOADB Tamil glyph names #30
  • Check vertical matrix and set
  • Design Improvements
  • Check Interpolation
  • Debug interpolation
  • Update copyright notices (On repo, source files, OFL, tables)
@pathumego pathumego added this to the Release 1.0.1 milestone Sep 8, 2015
@davelab6
Copy link
Contributor

This may need to go in a 2nd family.

@pathumego
Copy link
Member Author

Sinhala and Tamil don't share Unicode points. Is it possible to ship it
combined? Or is it like Latin+ somescript

On Sat, Sep 12, 2015, 3:46 AM Dave Crossland [email protected]
wrote:

This may need to go in a 2nd family.


Reply to this email directly or view it on GitHub
#16 (comment)
.

@pathumego
Copy link
Member Author

@davelab6 Tamil dose share unicode points /zwj and /nzwj is there. So how should it be? A separate repo for Tamil I guess? If so we have to have separate repos for other Tamil projects too I guess.

@davelab6
Copy link
Contributor

Yeah I think for now lets ship them as 2 families. Do you want to keep the Abhaya family name for both? I'm not sure... up to you :)

@davelab6
Copy link
Contributor

I guess that eventually the W3C will fix unicode range, and then we can ship combined families and de-list the duplicates

@pathumego
Copy link
Member Author

From the Google Fonts mailing list

1. Should we have two separate repos for this?
2. Or treat it as a one family in production(in same repo, under same family name) and only consider it as two families for Google Fonts shipping?  
3. Can we keep the same family name for both fonts?

In the Fonts API, you can't have the same name for both families... perhaps use Abhaya Libre for the Latin + Sinhala and Something Libre for the Latin + Tamil? Or Abhaya Libre for Latin + Sinhala and Abhaya Libre Something or Abhaya Something Libre for the Latin + Tamil?

Do the overlapping unicodes need to be different? If not, I suggest that (2) can be better - you develop a single repo and build combined font binaries, and use pyftsubset and fontTools to split and rename them into latin-plus-another-script pieces.

@pathumego pathumego changed the title Add Tamil Glyphs Tamil Support Feb 12, 2017
@pathumego
Copy link
Member Author

This is progressing in https://github.com/mooniak/abhaya-libre-font/tree/dev

@pathumego pathumego removed the ready label May 26, 2021
@pathumego pathumego self-assigned this May 26, 2021
@pathumego
Copy link
Member Author

Google Fonts can now ship this as a single family. With AbhayaL Libre version 2 we will ship Sinhala, Tamil and Latin in a single family. Tracking progress here #67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants