aboutsummaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorAkshay <[email protected]>2020-03-17 16:53:49 +0000
committerAkshay <[email protected]>2020-03-17 16:53:49 +0000
commit214e6cb76772989324be55c3ffa2d39dfa296295 (patch)
tree42648e31ff2dde5199c63eccda46966cbd077667 /posts
parent9227a05c650c12fb45d8cf6497165d2641335438 (diff)
new post: Font Size Fallacies
Diffstat (limited to 'posts')
-rw-r--r--posts/font_size_fallacies.md81
1 files changed, 81 insertions, 0 deletions
diff --git a/posts/font_size_fallacies.md b/posts/font_size_fallacies.md
new file mode 100644
index 0000000..e795135
--- /dev/null
+++ b/posts/font_size_fallacies.md
@@ -0,0 +1,81 @@
1I am not an expert with fonts, but I do have some
2experience [^exp], and common sense. This post aims to debunk some
3misconceptions about font sizes!
4
5[^exp]: https://github.com/nerdypepper/scientifica
6
711 px on your display is *probably not* 11 px on my display.
8Let's do some quick math. I have two displays, 1366x768 @
921" and another with 1920x1080 @ 13", call them `A` and
10`B` for now.
11
12Display `A` has 1,049,088 pixels. A pixel is a square, of
13side say, `s` cm. The total area covered by my 21" display
14is about 1,066 cm^2 (41x26). Thus,
15
16```
17Display A
18Dimensions: 1366x768 @ 21" (41x26 sq. cm)
191,049,088 s^2 = 1066
20 s = 0.0318 cm (side of a pixel on Display A)
21```
22
23Bear with me, as I repeat the number crunching for Display
24`B`:
25
26```
27Display B
28Dimensions: 1920x1080 @ 13" (29.5x16.5 sq. cm)
292,073,600 s^2 = 486.75
30 s = 0.0153 cm (side of a pixel on Display B)
31```
32
33The width of a pixel on Display `A` is *double* the width of a
34pixel on Display `B`. The area occupied by a pixel on Display
35`A` is *4 times* the area occupied by a pixel on Display `B`.
36
37*The size of a pixel varies from display to display!*
38
39A 5x11 bitmap font on Display `A` would be around 4 mm tall
40whereas the same bitmap font on Display `B` would be around
411.9 mm tall. A 11 px tall character on `B` is visually
42equivalent to a 5 px character on `A`. When you view a
43screenshot of Display `A` on Display `B`, the contents are
44shrunk down by a factor of 2!
45
46So screen resolution is not enough, how else do we measure
47size? Pixel Density! Keen readers will realize that the 5^th
48grade math problem we solved up there showcases pixel
49density, or, pixels per cm (PPCM). Usually we deal with
50pixels per inch (PPI).
51
52**Note:** PPI is not to be confused with DPI [^dpi] (dots
53per inch). DPI is defined for printers.
54
55[^dpi]: https://en.wikipedia.org/wiki/Dots_per_inch
56
57In our example, `A` is a 75 ppi display and `B` is around
58165 ppi [^ppi]. A low ppi display appears to be
59'pixelated', because the pixels are more prominent, much
60like Display `A`. A higher ppi usually means you can view
61larger images and render crispier fonts. The average desktop
62display can stuff 100-200 pixels per inch. Smart phones
63usually fall into the 400-600 ppi (XXXHDPI) category. The
64human eye fails to differentiate detail past 300 ppi.
65
66*So ... streaming an 8K video on a 60" TV provides the same
67clarity as a HD video on a smart phone?*
68
69Absolutely. Well, clarity is subjective, but the amount of
70detail you can discern on mobile displays has always been
71limited. Salty consumers of the Xperia 1 [^sony] will say
72otherwise.
73
74[^sony]: https://en.wikipedia.org/wiki/Sony_Xperia_1
75
76Maybe I will talk about font rendering in another post, but
77thats all for now. Don't judge a font size by its
78screenshot.
79
80[^ppi]: https://www.sven.de/dpi/
81