Description:
As of the latest freetype2 updates(2.10) it now uses the `defaultChar' property of PCF fonts to set the glyph for the undefined character at glyph index 0 (as FreeType already does for all other supported font formats). As a consequence, the order of glyphs of a PCF font if accessed with FreeType can be different now compared to previous versions. (https://sourceforge.net/projects/freetype/files/freetype2/2.10.0/)

This breaks a lot of PCF fonts in various ways, the most straight forward solution to this is to simply avoid the PCF format and use the BDF format, siji has also resolved it like this (https://github.com/stark/siji/issues/28).

Since the dina upstream provides these BDF formats, the fix would be pretty straight forward, for the time being I've put up this modified package on the aur as dina-font-bdf, but wanted to bring this issue to attention on this as well.

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
- install latest freetype2 version
- attempt to use dina or other pcf formatted fonts