<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: MonoLisa</title>
    <description>The latest articles on DEV Community by MonoLisa (@monolisafont).</description>
    <link>https://dev.to/monolisafont</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2862849%2F45cf7c01-84fa-466d-83f9-36f8a236cb8b.png</url>
      <title>DEV Community: MonoLisa</title>
      <link>https://dev.to/monolisafont</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/monolisafont"/>
    <language>en</language>
    <item>
      <title>What are font ligatures?</title>
      <dc:creator>MonoLisa</dc:creator>
      <pubDate>Tue, 22 Apr 2025 11:29:12 +0000</pubDate>
      <link>https://dev.to/monolisafont/what-are-font-ligatures-43il</link>
      <guid>https://dev.to/monolisafont/what-are-font-ligatures-43il</guid>
      <description>&lt;p&gt;Font ligatures are a type feature where two or more glyphs are joined together. The resulting glyph, the ligature, replaces the matched glyphs. In this post, we will explore this type feature and explain its pros and cons while showing how to enable the feature. Some developers find ligatures useful in their workflow as they can improve the legibility of their code, so it is worth it to understand what the feature is about.&lt;/p&gt;

&lt;h2&gt;
  
  
  When are ligatures used?
&lt;/h2&gt;

&lt;p&gt;If you look closely, you might notice that many fonts do something special with combinations of &lt;code&gt;fi&lt;/code&gt; and &lt;code&gt;ft&lt;/code&gt;. You might notice how letters are subtly joined together. Historically speaking, early typesetters would model the replacement letter as a single block for their printing machine, as mentioned by &lt;a href="https://ilovetypography.com/2007/09/09/decline-and-fall-of-the-ligature/" rel="noopener noreferrer"&gt;I love typography&lt;/a&gt;. Another interesting tidbit is that ampersand (&lt;code&gt;&amp;amp;&lt;/code&gt;) started as the combination of &lt;code&gt;E&lt;/code&gt; and &lt;code&gt;t&lt;/code&gt; and was a ligature before being formalized as an official letter. Similar examples can be found from Nordic letters of &lt;code&gt;Æ&lt;/code&gt;,&lt;code&gt;Œ&lt;/code&gt;, and the German letter &lt;code&gt;ß&lt;/code&gt;, which started as ligatures to improve legibility. The example below showcases several common ligatures from the MonoLisa typeface.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fygnhm3drdqjxn7mioedh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fygnhm3drdqjxn7mioedh.png" alt="Common ligatures (typeface: MonoLisa)" width="800" height="1005"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How are ligatures visible in the OpenType font specification?
&lt;/h2&gt;

&lt;p&gt;If you look at the OpenType font specification carefully, you can notice it contains &lt;a href="https://www.preusstype.com/techdata/otf_liga.php" rel="noopener noreferrer"&gt;liga&lt;/a&gt; and &lt;a href="https://www.preusstype.com/techdata/otf_dlig.php" rel="noopener noreferrer"&gt;dlig&lt;/a&gt; features. Both groups are meant for ligatures, and &lt;code&gt;liga&lt;/code&gt; contains combinations that should be used in normal conditions, while &lt;code&gt;dlig&lt;/code&gt; has been reserved for discretionary usage, and it is up to the user’s preference per the definition.&lt;/p&gt;

&lt;p&gt;MonoLisa typeface includes both, and the idea is that &lt;code&gt;liga&lt;/code&gt; contains more radical replacements while &lt;code&gt;dlig&lt;/code&gt; has been reserved for spacing-related tweaks, making it more subtle. It is possible that typefaces interpret the rules for your convenience like this, and it is a good idea to check what OpenType features they offer and how if you want to get the most out of the typefaces you use.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are coding ligatures?
&lt;/h2&gt;

&lt;p&gt;Now that you understand what ligatures are and why they are used, it is good to consider how they can be used for programming. Several coding fonts contain these combinations as ligatures to improve the legibility of common combinations, such as &lt;code&gt;!=&lt;/code&gt;. In other words, after replacement, the combination would stand out on its own, and often, you end up with a more mathematical look for your code that some programmers prefer. Given it is not a look all programmers like, it is possible to toggle the feature using &lt;code&gt;liga&lt;/code&gt; and &lt;code&gt;dlig&lt;/code&gt; OpenType flags, and even if a typeface contains ligatures, they aren’t enabled by default. Consider the figure below to get a better idea of what kind of coding ligatures are possible.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fk9xd0hwefdcfe7lfz9ka.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fk9xd0hwefdcfe7lfz9ka.png" alt="Coding ligatures (typeface: MonoLisa)" width="800" height="745"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;From the type designer’s point of view, providing ligatures for a coding font comes with some challenges. There is limited space to use since coding fonts are monospaced by definition and, therefore, take a fixed width. The key issue is to get the spacing and proportion right so that the resulting glyphs fit their context well.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Ligatures are a type feature that many typefaces contain to improve the legibility of certain letter combinations. Coding fonts provide ligatures specific to the task. In coding fonts, ligatures are an optional feature you can enable if you prefer the more math kind of look.&lt;/p&gt;

</description>
      <category>typography</category>
      <category>design</category>
      <category>typefaces</category>
    </item>
    <item>
      <title>What are serifs?</title>
      <dc:creator>MonoLisa</dc:creator>
      <pubDate>Mon, 17 Feb 2025 08:44:56 +0000</pubDate>
      <link>https://dev.to/monolisafont/what-are-serifs-4860</link>
      <guid>https://dev.to/monolisafont/what-are-serifs-4860</guid>
      <description>&lt;p&gt;You may have noticed that some typefaces have tiny legs or bars attached to their glyphs. These visual elements, serifs, have a specific purpose, and in this post, we will discuss the history of serifs, when you might want to serifed fonts, and when to avoid them in your designs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why were serifs invented?
&lt;/h2&gt;

&lt;p&gt;It has been speculated that the first serifs were invented out of necessity. Suppose you look at statues from the Roman era. In that case, you might notice their usage of serifs as the visual elements were used as terminators to allow easier cutting of characters into stone. You would cut the serif end first so that the remaining cuts would terminate neatly. In other words, serifs likely exist because of practical reasons. Since then, the original characters used by the Romans were modeled as a typeface called &lt;a href="https://en.wikipedia.org/wiki/Trajan_(typeface)" rel="noopener noreferrer"&gt;Trajan&lt;/a&gt; pictured in the image below. Trajan borrowed the characters from a roughly 2000-year-old column in Rome commemorating emperor Trajan's victory in the &lt;a href="https://en.wikipedia.org/wiki/Trajan%27s_Dacian_Wars" rel="noopener noreferrer"&gt;Dacian Wars&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fuhmb4sp7yqqxxakkk8ns.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fuhmb4sp7yqqxxakkk8ns.png" alt="Examples of serif fonts" width="800" height="821"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Baskerville" rel="noopener noreferrer"&gt;Baskerville&lt;/a&gt; is an example of a transitional serif typeface from the 1750s.&lt;br&gt;
It modernized older shapes, and the typeface is still prevalent in book design.&lt;/p&gt;

&lt;p&gt;Further evolution of serifs occurred in the 19th century as &lt;a href="https://en.wikipedia.org/wiki/Slab_serif" rel="noopener noreferrer"&gt;Slab Serif&lt;/a&gt; was introduced. The development of Slab Serif was motivated by the prevalence of printing press technologies and typewriters where each character had to be modeled on its own leading to monospaced fonts.&lt;/p&gt;

&lt;p&gt;If you want to see a sans serif font vs. a serifed font, consider comparing &lt;a href="https://www.facetype.org/fonts/publica-sans" rel="noopener noreferrer"&gt;Publica Sans&lt;/a&gt; and &lt;a href="https://www.facetype.org/fonts/publica-slab" rel="noopener noreferrer"&gt;Publica Slab&lt;/a&gt;. The mood of the fonts is quite different and you can use this to your benefit especially in design work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why are serifs still in use?
&lt;/h2&gt;

&lt;p&gt;The simple answer is that serifs are still in use as they &lt;a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC4612630/" rel="noopener noreferrer"&gt;may be more legible&lt;/a&gt; given they provide hints for readers to allow faster comprehension. A classic example is to pick up a typeface and consider characters, such as "l", "I", "1". Leaving serifs out leads to a design challenge in communicating the difference between the characters. Unfortunately, it is not always this straightforward as &lt;a href="https://geniusee.com/single-blog/font-readability-research-famous-designers-vs-scientists" rel="noopener noreferrer"&gt;other studies&lt;/a&gt; imply that sans serif (read: "without serif") can be the more legible option for children. The same applies to people with low vision, and the same applies even to digital displays.&lt;/p&gt;

&lt;p&gt;Serifs have their uses, especially in print and programming. The main benefit is that serifs allow a font designer to effectively address differences between characters when designing a monospaced font. It is even possible to selectively apply ideas from serifs to sans serif fonts to address specific design problems related to specific characters (i, j, r, and l are good examples). In monospaced fonts, serifs allow occupying space to avoid creating too large gaps between characters since the available space is fixed to a certain width.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bonus serif - flare serifs
&lt;/h2&gt;

&lt;p&gt;Although it is not considered a real serif, the so-called flare serif is an interesting special case as it achieves a similar effect by varying width without introducing a serif. &lt;a href="https://en.wikipedia.org/wiki/Optima" rel="noopener noreferrer"&gt;Optima&lt;/a&gt; is a good example of a typeface implementing this technique.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Serifs go way back, and they still have their uses even today. Even if you might not use serifs fonts always, they have specific strengths, and they can be instrumental in monospaced typefaces to improve the legibility of characters through additional hints to allow faster character recognition, not to mention the space-filling benefits of serifs. Now that you know what serifs are, it isn't easy to unsee them.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;If you want to discover more serif typefaces, &lt;a href="https://en.wikipedia.org/wiki/Category:Serif_typefaces" rel="noopener noreferrer"&gt;see Wikipedia's serif-related categories&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>typefaces</category>
      <category>design</category>
      <category>typography</category>
    </item>
  </channel>
</rss>
