I've tried using calt but it's not really working - i.e. it works fine in FontForge but generated fonts seem to ignore it.
feature calt {
pos @wide @narrow' <128 0 0 0> @narrow;
} calt;
You can see the feature file here:
https://github.com/larsenwork/monoid/blob/master/Utilities/RegularKerning.feaI can't use standard kerning as the font is monospaced.
Any suggestions? (I'm a bit new to all this - just playing around with the possibilities.
Comments
How does one compile using makeOTF?
Any help is much appreciated.
https://github.com/larsenwork/monoid/blob/master/Utilities/All.fea
Is there an automated way to generate that DB file...?
In short – makeotf requires a number of files:
• features
If you put them all in one directory then the following command should be sufficient:
@Paul van der Laan Cheers - I've been reading through some of it already. It's terribly written. Not beginner friendly:) Says there is an example GlyphOrderAndAliasDB in a folder where there is none etc.
Is there an automated way to generate GlyphOrderAndAliasDB ?
If you don’t want to rename any glyphs during compilation, then finalGlyphname will be the same as currentGlyphname. The third column with unicodes is optional. For example:
@Georg Seifert do you mind explaining me (beginner friendly) how you got it working?
FontForge is a bit more tolerant than the AFDKO. If I compile your features with OTM, I get the following error message: ‘HOT [ERROR] The languagesystem DFLT dlft; statement must precede all other language system statements.’ After fixing this everything seems to work fine from a technical point of view (although the result using DTL Argo is probably not what you had in mind ;-).
@Paul thanks for links, will have to get into using FKO at some point:)