Changelog¶
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
v2.0.0 - 2022-01-14¶
Added:
- This changelog!
- Documentation for the
FontFiller.missing_chars
andFontFiller.unknown_classes
attributes. Font
now stores the standard BDF fields as attributes (name
,ptSize
,xdpi
,ydpi
).bdflib.xlfd
makes it easy to check whether a font conforms to the X Logical Font Descriptor conventions, and to automatically fix many conformance problems.
Changed:
- Now that
Font
stores BDF fields in standard attributes, and now thatbdflib.xlfd
exists, theFont
class no longer needs to assume BDF custom properties are used for anything in particular. In particular, the standard BDF fields are no longer mirrored to XLFD-style properties, there’s no special property names that cannot be overwritten, and XLFD properties will no longer be automatically synthesised when writing out a BDF font. - The
Glyph
constructor (and thereforeFont.new_glyph_from_data()
) now takes bitmap data in the form of a list of integers, not the hex-encoded string used in the BDF on-disk format.
Removed:
- Support for Python 2.x
- Support for fonts whose point-size (the first parameter to the SIZE field in the font header) is a non-integer. I don’t know why I ever thought this was a good idea.
v1.1.3 - 2019-04-23¶
Fixed:
- We now support BDF comments in more places (although all the comments in a file are still concatenated)
- We now support values being separated from keywords by more than a single space.
v1.1.2 - 2019-04-22¶
Added:
- The examples in the API reference and tutorial are now automatically tested.
Fixed:
- The documentation now includes the tutorial.bdf file used by the tutorial.
v1.1.0 - 2018-11-19¶
Added:
- Standalone documentation, including a tutorial
- The
Glyph.iter_pixels()
method, making it easier to get at the glyph bitmap data.
Fixed:
FontFiller
now supports supports generating spacing characters made from only combining characters.