Skip to content

Commit

Permalink
Add supporting fonts for fontforge/fontforge#4668
Browse files Browse the repository at this point in the history
  • Loading branch information
elmimmo committed Apr 14, 2021
1 parent 86de477 commit 8dda4c6
Show file tree
Hide file tree
Showing 6 changed files with 25 additions and 0 deletions.
Binary file added AVAKerBol.bin
Binary file not shown.
Binary file added AVAKerBolIta.bin
Binary file not shown.
Binary file added AVAKerIta.bin
Binary file not shown.
Binary file added AVAKerReg.bin
Binary file not shown.
Binary file added AVAKern.bin
Binary file not shown.
25 changes: 25 additions & 0 deletions AVAKern.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
Associated with FontForge bug #4668:
https://github.com/fontforge/fontforge/issues/4668

This is a sample Mac Type 1 font suitcase with its associated outline
files, for a font family named AVAKern with four styles: Regular,
Italic, Bold and Bold Italic. AVAKern.bin is the font suitcase itself.
AVAKerReg.bin, AVAKerIta.bin, AVAKerBol.bin and AVAKerBolIta.bin are
the associated outline files.

The font suitcase contains, among other data, kerning info for the
associated outline files. Particularly, it has very obvious negative
kerning for the following pairs in all four styles: AV, VA, av and va.

In order to open the outlines in FontForge’s GUI and retain the kerning
info, one needs to first open an outline file and then go to menu File
> Merge Feature Info > AVAKern.bin.

The fonts were generated with FontLab 5 Studio Demo, which heavily
restricts the number of glyphs. Therefore, all four styles only have
characters A-C, S-X, all in the shape of upper case. The outlines were
copied from Source Sans (and then Fontlab watermarked some).

All five files were MacBin-encoded so that they survive in non-Mac
filesystems. AFAIK, FontForge can still transparently load them without
any intermediate decoding.

0 comments on commit 8dda4c6

Please sign in to comment.