aboutsummaryrefslogtreecommitdiff
path: root/docs/posts/bye_bye_BDFs.html
blob: 3b20814a02ef7e5b84516dccc4cbb0a61d374ccb (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<!DOCTYPE html>
<html lang="en">
  <head>
    <link rel="stylesheet" href="/style.css">
    <meta charset="UTF-8">
    <meta name="viewport" content="initial-scale=1">
    <meta content="#ffffff" name="theme-color">
    <meta name="HandheldFriendly" content="true">
    <meta property="og:title" content="nerdypepper">
    <meta property="og:type" content="website">
    <meta property="og:description" content="a static site {for, by, about} me ">
    <meta property="og:url" content="https://nerdypepper.tech">
    <body>
      <div class="posts">
        <div class="post">
          <div class="date">07/08 2019</div>
          <span style="font-size: 2rem; font-weight: 600">
            Bye Bye BDFs
          </span>
          <div class="post-text">
            <p>Glyph Bitmap Distribution Format is no more, as the creators of
<a href="https://pango.org">Pango</a>, one of the most widely used text rendering
libraries,
<a href="https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/">announced</a>
their plans for Pango 1.44.</p>

<p>Until recently, Pango used FreeType to draw fonts. They will be moving over
to <a href="https://harfbuzz.org">Harfbuzz</a>, an evolution of FreeType.</p>

<p><em>Why?</em></p>

<p>In short, FreeType was hard to work with. It required complex logic, and 
provided no advantage over Harfbuzz (other than being able to fetch
opentype metrics with ease).</p>

<p>Upgrading to Pango v1.44 will break your GTK applications (if you use a
<code>bdf</code>/<code>pcf</code> bitmap font). Harfbuzz <em>does</em> support bitmap-only OpenType fonts,
<code>otb</code>s. Convert your existing fonts over to <code>otb</code>s using
<a href="https://fontforge.github.io">FontForge</a>. It is to be noted that applications
such as <code>xterm</code> and <code>rxvt</code> use <code>xft</code> (X FreeType) to render fonts, and will
remain unaffected by the update.</p>

<p>Both <a href="https://github.com/nerdypepper/scientifica">scientifica</a> and
<a href="https://github.com/nerdypepper/curie">curie</a> will soon ship with bitmap-only
OpenType font formats.</p>

          </div>
          <a href="/index.html" class="post-end-link">← Back</a>
          <div class="separator"></div>
        </div>
      </div>
    </body>
</html>