shadowfacts/fonttools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[glyf] Align glyphs at word boundaries, not long

Browse Source 
Saves two bytes per glyph on average.  Or as Roozbeh reports,
70kb in DroidSansFallbackFull.ttf.
This commit is contained in:
Behdad Esfahbod 2014-07-14 19:53:42 -04:00
parent 68921c97ea
commit 671bca785d
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Lib/fontTools/ttLib/tables/_g_l_y_f.py
View File

@ -247,11 +247,15 @@ class Glyph(object):
else: else:
data = data + self.compileCoordinates() data = data + self.compileCoordinates()
# From the spec: "Note that the local offsets should be word-aligned" # From the spec: "Note that the local offsets should be word-aligned"
# From a later MS spec: "Note that the local offsets should be long-aligned" # From a later MS spec: "Note that the local offsets should be long-aligned,
# Let's be modern and align on 4-byte boundaries. # Offsets which are not long-aligned may seriously degrade performance of
if len(data) % 4: # some processors." We don't believe that long-alignment is required or
# has significant implications, so we align by two, which on average
# saves two bytes per glyph.
alignment = 2
if len(data) % alignment:
# add pad bytes # add pad bytes
nPadBytes = 4 - (len(data) % 4) nPadBytes = alignment - (len(data) % alignment)
data = data + b"\0" * nPadBytes data = data + b"\0" * nPadBytes
return data return data