Add Iosevka programming font

[aternummus]

Hi Ryan,
this is the suggested reminder ;-)
PLEASE work your magic on the Iosevka font familiy:
https://github.com/be5invis/Iosevka

[ryanoasis]

Yep thanks for creating an issue. I'll aim for next release. Cheers 😄

[be5invis]

There are some very low-level operations are performed when building Iosevka (like forcing a OS/2.xCharWidth and adding a DSIG), I'm not sure whether this patching script can preserve this.
Perhaps you can checkout otfcc, which is used to build the fonts with direct control (and optimizations).

[ryanoasis]

@be5invis Thanks for chiming in 😄

I appreciate your feedback and warnings. 👍

I will have to look more into it but I think FontForge can only provide a 'dummy' DSIG which I only currently understand to provide Windows compatibility.

You are right possibly the current patch script can't do a complete job and given your feedback maybe it is best to link to a new issue with the items you mentioned from the readme (we did something similar with Hack linking to #70).

Overall I am pretty naive about the points you mentioned, so unless you are highly against us patching your font I will move forward. Please let me know either wary 😊

Side note: I am really liking the look of Iosevka so far and will be giving it a test run in my editor for a while. 😄

[be5invis]

@ryanoasis A patching workflow proposal:

1. Dump Iosevka and your symbol font (as .ttf, without Powerline symbols) into JSON using otfccdump. Add glyph name prefix if necessary.
2. Write a program to merge them. Two main tables, cmap and glyf, should be merged. (I do not think that this symbol font has OpenType features. If so, these tables should also be merged.)
3. Build a patched font using otfccbuild --keep-average-char-width --ship.
4. Re-hint it using ttfautohint.

[ryanoasis]

@be5invis Hey thanks a lot. I will seriously consider drastically changing certain build processes. I am going to open a separate ticket however since this one will be closed for 0.8.0 release

[be5invis]

@ryanoasis Opened #83

[ryanoasis]

@be5invis Great, perfect. Thanks

[github-actions]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.