This repository has been archived by the owner on Jun 4, 2022. It is now read-only.
Releases: caryll/otfcc
Releases · caryll/otfcc
otfcc r0.2.1
- This release adds a primitive optimizer for CFF writer, which reduces the final file size at about 15%.
- Fixes the classdef writer when all glyphs are assigned to class 0.
otfcc r0.2.0
otfcc supports CFF now.
The CFF metadata are exported to the CFF_
field, while outlines are still in the glyf
field, preserving the same format with TTF.
otfcc r0.1.9
Now otfccbuild
preserves chain rules without any lookup application. It is necessary when deal with AFDKO's ignore sub
.
otfcc r0.1.8
- Added
--glyph-name-prefix <pfx>
inotfccdump
to add a prefix to all glyph names.
otfcc r0.1.7
- When dumping a font, GID 0 will always be named as ".notdef" unless the POST table specified its name.
- Supported
lookupOrder
entry to specify order of lookups.
otfcc r0.1.6
- The format 4 subtable's "ending cap" FFFF-FFFF mapping is corrected to satisfy OTS.
- The script list and feature list is sorted to satisfy some Windows programs.
otfcc r0.1.5
- The entries in [name] table will be automatically ordered, following OTSpec.
- Added
--ship
option to maximally reduce file size, used for shipping fonts.
otfcc r0.1.4
- Optimized the dump output of "flag" fields, like
OS/2.fsSelection
.otfcc
now will dump them as objects with easy-to-read field names. head.modified
will be automatically set to current time when building a font. Use--keep-modified-time
to use the value specified in JSON.
otfcc r0.1.3
Changes in this release:
- Fixed crash when reading a TTF with zero-length coverages and classdefs.
- Added stating for head table.
- Added stating for maxp.numGlyphs.
- Added stating for post.maxMemoryType42.
- Removed redundant data when dumping to JSON.
otfcc r0.1.2
First public beta of otfcc
.
Supported font types:
- Reading OT/TT fonts, including TTCs
- Writing OT/TT fonts
Supported tables:
head
hhea
maxp
OS/2
post
glyf
andloca
hmtx
vhea
vmtx
fpgm
prep
cvt
gasp
GSUB
GPOS
GDEF
Windows binaries are listed below. (Windows users are lazy, they simply do not want to build the entire project from scratch.)