Afdko

Latest version: v4.0.2

Safety actively analyzes 690721 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 11 of 18

2.5.62690

-------------------------------

- [makeotf] When building output TTF font from an input TTF font,
will now suppress warnings that hints are missing. Added a new
option '-shw' to suppress these warnings for other fonts that with
unhinted glyphs. These warnings are shown only when the font is
built in release mode.
- [makeotfexe] If the cmap format 4 UTF16 subtable is too large to
write, then makeotfexe writes a stub subtable with just the first
two segments. The last two versions allowed using '-' in glyph
names. Removed this, as it breaks using glyph tag ranges in feature
files.
- Updated copyright, and removed patent references. Made extensive
changes to the source code tree and build process, to make it easier
to build the open source AFDKO. Unfortunately, the source code for
the **IS** and **checkOutlines** programs cannot be open sourced.
- [tx/mergeFonts/rotateFont] Removed '-bc' option support, as
this includes patents that cannot be shared in open source.
- [tx] All tx-related tools now report when a font exceeds the max
allowed subroutine recursion depth.
- [tx/mergeFonts/rotateFont] Added common options to all when
possible: all now support UFO and SVG fonts, the '-gx' option to
exclude fonts, the '-std' option for cff output, and the '-b'
option for cff output.

2.5.61944

-------------------------------

- [makeotf] Added new option '-gs'. If the '-ga' or '-r'
option is used, then '-gs' will omit from the font any glyphs
which are not named in the GOADB file.
- [Linux] Replaced the previous build (which worked only on 64-bit
systems) with a 32 bit version, and rebuilt checkOutlines with debug
messages turned off.
- [ttx] Fixed FDK/Tools/win/ttx.cmd file so that the 'ttx' command
works again.

2.5.61911

-------------------------------

- [makeotf] Add support for two new 'features' file keywords, for
the OS/2 table. Specifying 'LowerOpSize' and 'UpperOpSize' now
sets the values 'usLowerOpticalPointSize' and
'usUpperOpticalPointSize' in the OS/2 table, and set the table
version to 5.
- [makeotf] Fixed the '-newNameID4' option so that if the style
name is "Regular", it is omitted for the Windows platform name ID
4, as well as in the Mac platform version. See change in
build 61250.
- [tx] When the user does not specify an output destination file
path (in which case tx tries to write to stdout), tx now reports a
fatal error if the output is a UFO font, rather than crashing.
- [tx] Fixed crash when encountering an empty `<dict/>` XML
element.
- [spot] Added logic to dump the new fields in OS/2 table version 5,
**usLowerOpticalPointSize** and **usUpperOpticalPointSize**. An
example of these values can be seen in the Windows 8 system font
Sitka.TTC.
- [ufo workflow] Fixed autohint and checkOutlines so that the '-o'
option works, by copying the source UFO font to the destination UFO
font name, and then running the program on the destination UFO font.
- [ufo workflow] Fixed tools that the PostScript font name is not
required.
- Added Linux build.

2.5.61250

-------------------------------

- [tx] Fixed rare crashing bug in reading a font file, where a
charstring ends exactly on a refill buffer boundary.
- [tx] Fixed rare crashing bug in subroutinization.
- [tx] Fixed bug where it reported values for wrong glyph with more
than 32K glyphs in the font.
- [tx] Fixed bug where the tool would not dump a TrueType Collection
font file that contained OpenType/CFF fonts.
- [tx] Fixed issue where it failed to read a UFO font if the UFO
font lacked a fontinfo.plist file, or a psFontName entry.
- [IS] Fixed IS so that it no longer scales the fontDict FontMatrix,
when a scale factor is supplied, unless you provide an argument to
request this.
- [makeotf] The option '-newNameID4' now builds both Mac and Win
name ID 4 using name ID 1 and 2, as specified in the OpenType spec.
The style name is omitted from name ID 4 it is "Regular".
- [makeotf] Changed logic for specifying ValueFormat for PosPair
value records. Previous logic always used the minimum ValueFormat.
Since changing ValueFormat between one PosPair record and the next
requires starting a new subtable, feature files that used more than
one position adjustment in a PosPair value record often got more
subtable breaks then necessary, especially when specifying a PairPos
statement with an all zero Value Record value after a PairPos
statement with a non-zero Value Record. With the new logic, if the
minimum ValueFormat for the new ValueRecord is different than the
ValueFormat used with the ValueRecord for the previous PairPos
statement, and the previous ValueFormat permits expressing all the
values in the current ValueRecord, then the previous ValueFormat is
used for the new ValueRecord.
- Added commands **otc2otf** and **otf2otc** to build OpenType
collection files from a OpenType font files, and vice-versa.
- [ttx] Updated the FontTools library to the latest build on the
GitHub branch maintained by Behdad Esfahbod, as of Jan 14 2014.
- [ufo workflow] Fixed bugs in ufoTools.py. The glyph list was being
returned in alphabetic order, even when the public.glyphOrder key
was present in lib.py. Failed when the glyphOrder key was missing.

2.5.60908

-------------------------------

- [tx] Can now take UFO font as a source font file for all outputs
except rasterization. It prefers GLIF file from the layer
`glyphs.com.adobe.type.processedGlyphs`. You can select another
preferred layer with the option '-altLayer `<layer name>`'. Use
'None' for the layer name in order to have tx ignore the preferred
layer and read GLIF files only from the default layer.
- [tx] Can now write to a UFO with the option '-ufo'. Note that it
is NOT a full UFO writer. It writes only the information from the
Postscript font data. If the source is an OTF or TTF font, it will
not copy any of the meta data from outside the font program table.
Also, if the destination is an already existing UFO font, tx will
overwrite it with the new data: it will not merge the new font data
with the old.
- [tx] Fixed bugs with CID values \> 32K: used to write these as
negative numbers when dumping to text formats such as AFM.
- [autohint/checkOutlines] These programs can now be used with UFO
fonts. When the source is a UFO font, the option '-o' to write to
another font is not permitted. The changed GLIF files are written to
the layer 'glyphs.com.adobe.type.processedGlyphs'. Each script
maintains a hash of the width and marking path operators in order to
be able to tell if the glyph data in the default layer has changed
since the script was last run. This allows the scripts to process
only those glyphs which have changed since the last run. The first
run of autohint can take two minutes for a 2000 glyph font; the
second run takes less then a second, as it does not need to process
the unchanged glyphs.
- [stemHist/makeotf] Can now take UFO fonts as source fonts.

2.5.60418

-------------------------------

- [autohint] Now skips comment lines in fontinfo file.
- [makeotf] Added support for source font files in the 'detype1'
plain text format. Added logic for "Language" keyword in fontinfo
file; if present, will attempt to set the CID font makeotf option
-"cs" to set he Mac script value.
- [compareFamily] Added check in Family Test 10 that font really is
monospaced or not when either the FontDict isFixedPitch value or the
Panose value says that it is monospaced.
- [spot] Fixed bug that kept 'palt'/'vpal' features from being
applied when proofing kerning.

Page 11 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.