<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>fortes.com - Latest Comments in Enabling Ligatures in Avalon</title><link>http://fortes.disqus.com/</link><description></description><language>en</language><lastBuildDate>Sat, 02 Apr 2005 19:59:24 -0000</lastBuildDate><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207652</link><description>Kenny: Of the fonts that currently ship with Windows, only Palatino Linotype supports Ligatures. Most quality OpenType fonts today support ligatures, since they are an important factor in quality text.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fortes</dc:creator><pubDate>Sat, 02 Apr 2005 19:59:24 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207646</link><description>Kenny: Of the fonts that currently ship with Windows, only Palatino Linotype supports Ligatures. Most quality OpenType fonts today support ligatures, since they are an important factor in quality text.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fortes</dc:creator><pubDate>Sat, 02 Apr 2005 19:59:24 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207645</link><description>What other fonts are supporting ligatures?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kenny</dc:creator><pubDate>Fri, 01 Apr 2005 09:46:00 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207651</link><description>What other fonts are supporting ligatures?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kenny</dc:creator><pubDate>Fri, 01 Apr 2005 09:46:00 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207644</link><description>Correct TPhinney -- I only used Palatino in this example because it is one of the few fonts currently included with Windows that actually supports ligatures.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fortes</dc:creator><pubDate>Thu, 31 Mar 2005 18:12:35 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207650</link><description>Correct TPhinney -- I only used Palatino in this example because it is one of the few fonts currently included with Windows that actually supports ligatures.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fortes</dc:creator><pubDate>Thu, 31 Mar 2005 18:12:35 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207643</link><description>fil is right. Using Palatino for this example is kind of funny, because it was created so that the tops of the f's are very short, to avoid collisions (in the Linotype hot metal typesetting it was designed for). So it really doesn't matter so much for Palatino. But in many typefaces this is an important/useful feature.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tphinney</dc:creator><pubDate>Thu, 31 Mar 2005 17:21:59 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207649</link><description>fil is right. Using Palatino for this example is kind of funny, because it was created so that the tops of the f's are very short, to avoid collisions (in the Linotype hot metal typesetting it was designed for). So it really doesn't matter so much for Palatino. But in many typefaces this is an important/useful feature.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tphinney</dc:creator><pubDate>Thu, 31 Mar 2005 17:21:59 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207642</link><description>The effect is a bit easier to understand when you consider the f-i ligature. When you try properly type-set and space those adjacent letters, they will collide. Ligatures were created to deal with this problem.&lt;br&gt;&lt;br&gt;Also: Pretty much any book, newspaper, and magazine use ligatures in their printing, so you grow up reading (and recognizing) those letter and word shapes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fortes</dc:creator><pubDate>Thu, 10 Mar 2005 12:13:44 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207648</link><description>The effect is a bit easier to understand when you consider the f-i ligature. When you try properly type-set and space those adjacent letters, they will collide. Ligatures were created to deal with this problem.&lt;br&gt;&lt;br&gt;Also: Pretty much any book, newspaper, and magazine use ligatures in their printing, so you grow up reading (and recognizing) those letter and word shapes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fortes</dc:creator><pubDate>Thu, 10 Mar 2005 12:13:44 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207647</link><description>Not to be a pain, but are connected F's a good thing for readability in today's type-driven world?  On a lower cognition level it seems that recognizing that the single character created by joining two F's represents two seperate characters adds computation time (for our minds).  I've always thought that connecting written characters, such as cursive and this example, were _writing_ shortcuts - not _reading_ shortcuts?  But then, I am no expert :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mcbarron</dc:creator><pubDate>Thu, 10 Mar 2005 11:49:10 -0000</pubDate></item><item><title>Re: Enabling Ligatures in Avalon</title><link>http://fortes.com/2005/03/ligatures/#comment-1207641</link><description>Not to be a pain, but are connected F's a good thing for readability in today's type-driven world?  On a lower cognition level it seems that recognizing that the single character created by joining two F's represents two seperate characters adds computation time (for our minds).  I've always thought that connecting written characters, such as cursive and this example, were _writing_ shortcuts - not _reading_ shortcuts?  But then, I am no expert :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mcbarron</dc:creator><pubDate>Thu, 10 Mar 2005 11:49:10 -0000</pubDate></item></channel></rss>