diff options
author | NerdyPepper <[email protected]> | 2019-08-07 18:26:08 +0100 |
---|---|---|
committer | NerdyPepper <[email protected]> | 2019-08-07 18:26:08 +0100 |
commit | 7f39c8d77ed8dd60a60fa1ec3d31b3d8616abc1a (patch) | |
tree | 95d7b775d1671c443043fc77a2a787849baeb6ba /posts | |
parent | 681a65f85233ec68c3917e72c558cf2ad4e508d1 (diff) |
new post - bye bye bdfs
Diffstat (limited to 'posts')
-rw-r--r-- | posts/bye_bye_BDFs.md | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/posts/bye_bye_BDFs.md b/posts/bye_bye_BDFs.md new file mode 100644 index 0000000..487d7cb --- /dev/null +++ b/posts/bye_bye_BDFs.md | |||
@@ -0,0 +1,25 @@ | |||
1 | Glyph Bitmap Distribution Format is no more, as the creators of | ||
2 | [Pango](https://pango.org), one of the most widely used text rendering | ||
3 | libraries, | ||
4 | [announced](https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/) | ||
5 | their plans for Pango 1.44. | ||
6 | |||
7 | Until recently, Pango used FreeType to draw fonts. They will be moving over | ||
8 | to [Harfbuzz](https://harfbuzz.org), an evolution of FreeType. | ||
9 | |||
10 | *Why?* | ||
11 | |||
12 | In short, FreeType was hard to work with. It required complex logic, and | ||
13 | provided no advantage over Harfbuzz (other than being able to fetch | ||
14 | opentype metrics with ease). | ||
15 | |||
16 | Upgrading to Pango v1.44 will break your GTK applications (if you use a | ||
17 | `bdf`/`pcf` bitmap font). Harfbuzz *does* support bitmap-only OpenType fonts, | ||
18 | `otb`s. Convert your existing fonts over to `otb`s using | ||
19 | [FontForge](https://fontforge.github.io). It is to be noted that applications | ||
20 | such as `xterm` and `rxvt` use `xft` (X FreeType) to render fonts, and will | ||
21 | remain unaffected by the update. | ||
22 | |||
23 | Both [scientifica](https://github.com/nerdypepper/scientifica) and | ||
24 | [curie](https://github.com/nerdypepper/curie) will soon ship with bitmap-only | ||
25 | OpenType font formats. | ||