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

lohitize script? #9

Open
davelab6 opened this issue Mar 5, 2014 · 3 comments
Open

lohitize script? #9

davelab6 opened this issue Mar 5, 2014 · 3 comments

Comments

@davelab6
Copy link

davelab6 commented Mar 5, 2014

In http://pravin-s.blogspot.in/2013/11/how-to-lohit-ise-open-type-fonts-not.html @pravins writes that to 'lohitize' a font you can follow 6 steps:

  1. git clone https://github.com/pravins/lohit2
  2. cd lohit2/devanagari (or the appropriate orthography)
  3. cp "yourfont.ttf" .
  4. open yourfont.ttf in fontforge and save as a yourfont.sfd
  5. open yourfont.sfd and update glyphs names as per lohit fonts.
  6. python ../scripts/apply_featurefile.py yourfont.sfd Lohit-.fea - this only import gsub of lohit project, it will keep gpos tables intact.

Step 4 could be easily automated with a 3 line script.

Step 5 could also be automated, perhaps by using github.com/davelab6/pyfontaine when it is extended to check glyphnames as well as unicode points (this month I expect)

Step 6, what is the purpose of keeping gpos tables in tact? And what if they are missing? :)

I suggest making a lohitize.py scrip that does this automatically :)

@pravins
Copy link
Owner

pravins commented Mar 5, 2014

Yeah, good idea to automate this one. I was thinking this specifically for existing fonts around not updated from long time. Existing fonts will have gpos for specific to there design, so it is not necessary but for new font it is.

Agree with your idea for automating this task.

@davelab6
Copy link
Author

davelab6 commented Mar 5, 2014

Yes, I have a lot of such fonts already :)

The glyph names are normalized so the standard lohit gsub tables can be used.

To use standard gpos tables in the same way, we need the anchor names to be normalised?

(I mean, we shouldn't have custom GPOS/GSUB tables in lohitized fonts; they should depend on the upstream tables, which are maintained by @snehakore , and then as the upstream makes improvements, all the lohitized fonts will benefit)

@pravins
Copy link
Owner

pravins commented Mar 5, 2014

GPOS tables cant be standard, since those are keeps on changing as per design of font.
One can import GPSO from lohit2, but then he need to do manual work to update it as per his design.

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

No branches or pull requests

2 participants