2016-11-15 12:10:21 +00:00
|
|
|
# MicroPython font handling
|
2016-10-22 10:28:23 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
This repository defines a method of creating and deploying fonts for use with
|
|
|
|
MicroPython display drivers. A PC utility converts industry standard font files
|
|
|
|
to Python sourcecode and a MicroPython module enables these to be rendered to
|
|
|
|
suitable device drivers, notably OLED displays using the SSD1306 chip.
|
2016-10-29 10:35:13 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
# Introduction
|
2016-10-22 10:28:23 +00:00
|
|
|
|
|
|
|
MicroPython platforms generally have limited RAM, but more abundant storage in
|
|
|
|
the form of flash memory. Font files tend to be relatively large. The
|
|
|
|
conventional technique of rendering strings to a device involves loading the
|
2016-10-29 10:35:13 +00:00
|
|
|
entire font into RAM. This is fast but RAM intensive. The alternative of storing
|
2018-07-04 06:38:00 +00:00
|
|
|
the font as a random access file and loading individual glyphs into RAM on
|
2016-10-22 10:28:23 +00:00
|
|
|
demand is too slow for reasonable performance on most display devices.
|
|
|
|
|
|
|
|
This alternative implements a font as a Python source file, with the data being
|
2018-07-04 06:38:00 +00:00
|
|
|
declared as `bytes` objects. Such a file may be frozen as bytecode: this
|
|
|
|
involves building the firmware from source with the Python file in a specific
|
|
|
|
directory. On import very little RAM is used, yet the data may be accessed
|
|
|
|
fast. Note that the use of frozen bytecode is entirely optional: font files may
|
|
|
|
be imported in the normal way if RAM usage is not an issue.
|
2016-10-22 10:28:23 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
The resultant file is usable with two varieties of display device drivers:
|
2016-10-22 10:28:23 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
1. Drivers where the display class is subclassed from the official
|
|
|
|
`framebuffer` class.
|
2016-11-15 12:10:21 +00:00
|
|
|
2. Drivers for displays where the frame buffer is implemented in the display
|
2016-10-29 10:35:13 +00:00
|
|
|
device hardware.
|
2016-10-22 10:28:23 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
# Solution
|
2016-11-03 16:57:44 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
This comprises three components:
|
2016-11-03 16:57:44 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
1. [font_to_py.py](./FONT_TO_PY.md) This utility runs on a PC and converts a
|
2016-11-15 12:10:21 +00:00
|
|
|
font file to Python source. See below.
|
2018-08-14 16:22:21 +00:00
|
|
|
2. [The Writer class](./writer/WRITER.md) This facilitates rendering text to a
|
|
|
|
device having a suitably designed device driver.
|
|
|
|
3. [Device driver notes](./writer/DRIVERS.md). Notes for authors of display
|
|
|
|
device drivers. Provides details of the font file format and information on
|
|
|
|
ensuring comptibility with the `Writer` classes.
|
2016-11-03 16:57:44 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
# font_to_py.py
|
2016-10-29 10:35:13 +00:00
|
|
|
|
2018-08-14 16:22:21 +00:00
|
|
|
This command line utility is written in Python 3 and runs on a PC. It takes
|
2018-07-04 06:38:00 +00:00
|
|
|
as input a font file in `ttf` or `otf` form together with a height in pixels
|
2016-11-15 13:58:52 +00:00
|
|
|
and outputs a Python source file containing the font data. Fixed and variable
|
|
|
|
pitch rendering are supported. The design has the following aims:
|
2016-10-25 14:20:26 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
* Independence of specific display hardware.
|
|
|
|
* The path from font file to Python code to be fully open source.
|
2016-10-23 07:33:47 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
The first is achieved by supplying hardware specific arguments to the utility.
|
|
|
|
These define horizontal or vertical mapping and the bit order for font data.
|
2016-10-23 07:33:47 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
The second is achieved by using Freetype and the Freetype Python bindings. Its
|
|
|
|
use is documented [here](./FONT_TO_PY.md). This also details measurements of
|
|
|
|
RAM usage when importing fonts stored as frozen bytecode.
|
2016-10-23 07:33:47 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
# Limitations
|
2016-10-23 07:33:47 +00:00
|
|
|
|
2018-07-04 06:38:00 +00:00
|
|
|
By default the ASCII character set from `chr(32)` to `chr(126)` is supported
|
2017-01-12 16:03:36 +00:00
|
|
|
but command line arguments enable the range to be modified with extended ASCII
|
2018-07-04 06:38:00 +00:00
|
|
|
characters to `chr(255)` being included if required. Kerning is not supported.
|
2017-01-12 16:03:36 +00:00
|
|
|
Fonts are one bit per pixel. This does not rule out colour displays: the device
|
|
|
|
driver can add colour information at the rendering stage. It does assume that
|
|
|
|
all pixels of a character are rendered identically.
|
2016-10-23 07:33:47 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
Converting font files programmatically works best for larger fonts. For small
|
|
|
|
fonts, like the 8*8 default used by the SSD1306 driver, it is best to use
|
2017-01-12 16:03:36 +00:00
|
|
|
hand-designed binary font files: these are optiised for rendering at a specific
|
|
|
|
size.
|
2016-10-22 10:28:23 +00:00
|
|
|
|
2017-01-06 15:16:58 +00:00
|
|
|
# Font file interface
|
|
|
|
|
2018-07-04 06:38:00 +00:00
|
|
|
A font file is imported in the usual way e.g. `import font14`. It contains
|
2017-01-06 15:16:58 +00:00
|
|
|
the following methods which return values defined by the arguments which were
|
|
|
|
provided to font-to-py:
|
|
|
|
|
2018-07-04 06:38:00 +00:00
|
|
|
`height` Returns height in pixels.
|
|
|
|
`max_width` Returns maximum width of a glyph in pixels.
|
|
|
|
`hmap` Returns `True` if font is horizontally mapped. Should return `True`
|
|
|
|
`reverse` Returns `True` if bit reversal was specified. Should return `False`
|
|
|
|
`monospaced` Returns `True` if monospaced rendering was specified.
|
|
|
|
`min_ch` Returns the ordinal value of the lowest character in the file.
|
|
|
|
`max_ch` Returns the ordinal value of the highest character in the file.
|
2017-01-06 15:16:58 +00:00
|
|
|
|
2018-07-04 06:38:00 +00:00
|
|
|
Glyphs are returned with the `get_ch` method. Its argument is a character
|
2017-01-06 15:16:58 +00:00
|
|
|
and it returns the following values:
|
|
|
|
|
2018-07-04 06:38:00 +00:00
|
|
|
* A `memoryview` object containg the glyph bytes.
|
2017-01-06 15:16:58 +00:00
|
|
|
* The height in pixels.
|
|
|
|
* The character width in pixels.
|
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
# Licence
|
2016-10-22 10:28:23 +00:00
|
|
|
|
2016-11-15 12:10:21 +00:00
|
|
|
All code is released under the MIT licence.
|