<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>∃xistential Type</title>
	<atom:link href="http://existentialtype.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://existentialtype.net</link>
	<description>For People Who Like Type and Types</description>
	<lastBuildDate>Sat, 12 May 2012 16:35:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Fun with words</title>
		<link>http://existentialtype.net/2010/10/29/fun-with-words/</link>
		<comments>http://existentialtype.net/2010/10/29/fun-with-words/#comments</comments>
		<pubDate>Fri, 29 Oct 2010 15:00:12 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[humour]]></category>
		<category><![CDATA[types]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=386</guid>
		<description><![CDATA[I've always wanted to write a monkey inference system.]]></description>
			<content:encoded><![CDATA[<p>I've always wanted to write a <a href="http://thesaurus.com/browse/constraint">monkey</a> inference system.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2010/10/29/fun-with-words/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hibernation</title>
		<link>http://existentialtype.net/2010/10/01/hibernation/</link>
		<comments>http://existentialtype.net/2010/10/01/hibernation/#comments</comments>
		<pubDate>Sat, 02 Oct 2010 03:57:32 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[meta]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=379</guid>
		<description><![CDATA[Assuming anyone is still reading or subscribed to the RSS feed, you have probably noticed the marked lack of updates. There are a variety reasons for this. One is that I joined the compiler team at LogicBlox in January. As such, I am not really doing all that much typesetting or typographical sorts of things [...]]]></description>
			<content:encoded><![CDATA[<p>Assuming anyone is still reading or subscribed to the RSS feed, you have probably noticed the marked lack of updates.  There are a variety reasons for this.  One is that I joined the compiler team at <a href="http://logicblox.com/">LogicBlox</a> in January.  As such, I am not really doing all that much typesetting or typographical sorts of things these days.  Though I have been recently learning the joys of trying to produce HTML and PDF output from a <a href="http://www.docbook.org/">DocBook</a> source and have both look remotely reasonable.  As for type systems, well, I've been doing some of that, and may be doing quite a bit more in the near future.  But rather than worrying about whether I may say too much, I'm just saying nothing about that for maximal peace of mind.</p>
<p>So at this point I wouldn't expect much more anytime soon.  I have contemplated simply shutting the site down to further simplify my life, but there is still a steady readership for my LaTeX and fonts tutorial according to the analytics.</p>
<p>There was some renewed interest in my document <a href="http://existentialtype.net/2009/08/09/typographic-style-for-computer-scientists/">Typographic Style for Computer Scientists</a> on <a href="http://www.reddit.com/r/compsci/comments/dl90p/typographic_style_for_computer_scientists/">Reddit</a> yesterday, so maybe I will finally take some time to produce a new draft of that soonish.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2010/10/01/hibernation/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Mining Yahoo Images for color schemes</title>
		<link>http://existentialtype.net/2009/08/24/mining-yahoo-images-for-color-schemes/</link>
		<comments>http://existentialtype.net/2009/08/24/mining-yahoo-images-for-color-schemes/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 18:50:38 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[graphic design]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[color]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=336</guid>
		<description><![CDATA[I meant to post about this a while ago, but while reading Bruce Sterlings's Beyond the Beyond, I learned about this clever tool for generating color schemes. Given your keywords it searches for the top five images on Yahoo! Image Search and chooses the six most prominent colors from each. Perhaps unsurprisingly, given "existential type" [...]]]></description>
			<content:encoded><![CDATA[<p>I meant to post about this a while ago, but while reading <a href="http://www.wired.com/beyond_the_beyond/2009/07/peculiar-web-toy-may-in-fact-be-useful/">Bruce Sterlings's Beyond the Beyond</a>, I learned about <a href="http://www.gpeters.com/color/color-schemes.php">this clever tool for generating color schemes</a>.  Given your keywords it searches for the top five images on <a href="http://images.search.yahoo.com/">Yahoo! Image Search</a> and chooses the six most prominent colors from each.</p>
<p>Perhaps unsurprisingly, given "existential type" it just returns different shades of gray – ones even less interesting than Bruce got for "cyberpunk".</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/08/24/mining-yahoo-images-for-color-schemes/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Following up on quality fonts and meta-fonts</title>
		<link>http://existentialtype.net/2009/08/24/following-up-on-quality-fonts-and-meta-fonts/</link>
		<comments>http://existentialtype.net/2009/08/24/following-up-on-quality-fonts-and-meta-fonts/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 18:39:50 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[fonts]]></category>
		<category><![CDATA[meta]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[antykwa półtawskiego]]></category>
		<category><![CDATA[antykwa toruńska]]></category>
		<category><![CDATA[metatype1]]></category>
		<category><![CDATA[OCEANIA]]></category>
		<category><![CDATA[tex gyre]]></category>
		<category><![CDATA[type 1]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=333</guid>
		<description><![CDATA[In response to my post on quality fonts, mbana provided a pointer to a Typophile discussion on the Tex Gyre fonts. In particular, Thomas Phinney described their quality as "wildly variable". I suppose at the time I was using "quality" to more describe whether the fonts provided all the features I would expect to need, rather [...]]]></description>
			<content:encoded><![CDATA[<p>In response to my post on <a href="http://existentialtype.net/2009/04/12/quality-fonts/">quality fonts</a>, <a href="http://existentialtype.net/2009/04/12/quality-fonts/#comment-32696">mbana</a> provided a pointer to a <a href="http://typophile.com/node/41012">Typophile discussion on the Tex Gyre fonts</a>.  In particular, Thomas Phinney described their quality as "wildly variable".  I suppose at the time I was using "quality" to more describe whether the fonts provided all the features I would expect to need, rather than only aesthetic quality.  I have to admit when I did skim the specimens that they didn't look too bad to me. He did say that the glyphs based on the original URW designs were quite good, while the Greek and Cyrillic "range from mediocre to poor to largely useless".  Phinney most certainly has more experience with Cyrillic and type design than me, and arguably he probably just has a much better eye than me.</p>
<p><a href="http://existentialtype.net/2009/04/12/quality-fonts/#comment-32619">Leon</a> recommended <a href="http://junicode.sourceforge.net/">Junicode</a>, which provides the most important features I discussed.  I do think its stems are a bit thinner than I prefer, but it seems very well done.</p>
<p>In my discussion of <a href="http://existentialtype.net/2009/04/17/metatype1-and-meta-fonts/">METATYPE1 and meta-fonts</a>, <a href="http://existentialtype.net/2009/04/17/metatype1-and-meta-fonts/#comment-31737">Till</a> pointed out the existence of the meta-font <a href="http://www.ntg.nl/maps/25/13.pdf">Antykwa Półtawskiego</a>.  At the time I told him that I thought he was misinformed because <a href="http://nowacki.strefa.pl/torunska-e.html">Antykwa Toruńska</a> seemed to have been created by tracing scanned specimens.  A few days ago, <a href="http://titan.plasma.xg8.de:8080/~rtc/">Peter Backes</a> pointed out this rather egregious error in reading comprehension on my part. Currently, only the generated <a href="http://tug.ctan.org/tex-archive/fonts/psfonts/polish/antp/">Type 1 font files</a> are available for Antykwa Półtawskiego.  However, it sounds like it was prepared using a rather early version of METATYPE1 and therefore the sources could possibly be incompatible with the newer versions of METATYPE1.</p>
<p>Peter also noted that he has also created a font with METATYPE1 called <a href="http://titan.plasma.xg8.de:8080/~rtc/ocd108p0.pdf">OCEANIA</a>. It is perhaps not as "meta" as he thinks would be ideal, but during the time I've spent working with METAFONT and METATYPE1, I've definitely found that it is often quite difficult to come up with a reasonable declarative specification of a glyph.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/08/24/following-up-on-quality-fonts-and-meta-fonts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding symbols graphically</title>
		<link>http://existentialtype.net/2009/08/10/finding-symbols-graphically/</link>
		<comments>http://existentialtype.net/2009/08/10/finding-symbols-graphically/#comments</comments>
		<pubDate>Mon, 10 Aug 2009 15:22:01 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[fonts]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[detexify]]></category>
		<category><![CDATA[handwriting recognition]]></category>
		<category><![CDATA[latex]]></category>
		<category><![CDATA[symbols]]></category>
		<category><![CDATA[tex]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=329</guid>
		<description><![CDATA[Jeff pointed me to these extremely cool and useful web application: Detexify2.  At least a few of you readers have spent time skimming The Comprehensive LaTeX Symbol List looking for the incantation required for a specific symbol. With Detexify2 you can just scribble something that roughly looks the symbol and it will tell you the [...]]]></description>
			<content:encoded><![CDATA[<p>Jeff pointed me to these extremely cool and useful web application: <a href="http://detexify.kirelabs.org/classify.html">Detexify<sup>2</sup></a>.  At least a few of you readers have spent time skimming <a href="http://www.ctan.org/tex-archive/info/symbols/comprehensive/">The Comprehensive LaTeX Symbol List</a> looking for the incantation required for a specific symbol.  With Detexify<sup>2</sup> you can just scribble something that roughly looks the symbol and it will tell you the name and, if necessary, the LaTeX package that provides it.</p>
<p>The only problem is that it lets users help train the recognizer.  This can also be a good thing, but I can imagine a few malicious users (or perhaps just people with very bad drawing skills) ruining it for everyone.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/08/10/finding-symbols-graphically/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Typographic Style for Computer Scientists</title>
		<link>http://existentialtype.net/2009/08/09/typographic-style-for-computer-scientists/</link>
		<comments>http://existentialtype.net/2009/08/09/typographic-style-for-computer-scientists/#comments</comments>
		<pubDate>Sun, 09 Aug 2009 11:17:30 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[papers]]></category>
		<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=327</guid>
		<description><![CDATA[Typographic Style for Computer Scientists is a short article intended to bring computer scientists up to speed on typographical issues. I started writing it several years ago, and then set it aside for other projects. Recently, I decided rather than wait for it to be “complete” and perfect that I should polish it up a [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1em; margin-left: 0px; padding: 0px;"><a href="http://free-the-mallocs.com/_media/typographic-style.pdf">Typographic Style for Computer Scientists</a> is a short article intended to bring computer scientists up to speed on typographical issues. I started writing it several years ago, and then set it aside for other projects. Recently, I decided rather than wait for it to be “complete” and perfect that I should polish it up a little and see if people could benefit from it.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1em; margin-left: 0px; padding: 0px;">It is probably far from comprehensive, but hopefully some people will find it useful. I had been thinking of perhaps adding some material specifically on inference rules and judgments, but I am not sure what else it might make sense to include.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1em; margin-left: 0px; padding: 0px;">If you find mistakes please let me know. If you disagree on some of what I have said, let me know and perhaps I can address your concerns.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/08/09/typographic-style-for-computer-scientists/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>The Great Confusion</title>
		<link>http://existentialtype.net/2009/08/05/the-great-confusion/</link>
		<comments>http://existentialtype.net/2009/08/05/the-great-confusion/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 12:45:31 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=322</guid>
		<description><![CDATA[In the past forty-eight hours, I've written code in C++, F#, and Scala.  On top of that, XCode, Visual Studio, and Emacs all have different default keybindings for all the most common operations.  Then add in switching between US and Danish physical keyboard layouts.]]></description>
			<content:encoded><![CDATA[<p>In the past forty-eight hours, I've written code in C++, F#, and Scala.  On top of that, XCode, Visual Studio, and Emacs all have different default keybindings for all the most common operations.  Then add in switching between US and Danish physical keyboard layouts.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/08/05/the-great-confusion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing mftrace</title>
		<link>http://existentialtype.net/2009/04/18/testing-mftrace/</link>
		<comments>http://existentialtype.net/2009/04/18/testing-mftrace/#comments</comments>
		<pubDate>Sat, 18 Apr 2009 20:25:31 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[fonts]]></category>
		<category><![CDATA[graphic design]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[ams euler]]></category>
		<category><![CDATA[computer modern]]></category>
		<category><![CDATA[fontforge]]></category>
		<category><![CDATA[metafont]]></category>
		<category><![CDATA[metatype1]]></category>
		<category><![CDATA[mftrace]]></category>
		<category><![CDATA[tracing]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=306</guid>
		<description><![CDATA[I am not entirely sure how fair of a comparison I am making, but I am open to suggestions on how to better compare the hypothetical output of a font designed using METATYPE1, where a Type 1 font would be directly generated, versus a font designed using METAFONT, where a Type 1 font is generated [...]]]></description>
			<content:encoded><![CDATA[<p>I am not entirely sure how fair of a comparison I am making, but I am open to suggestions on how to better compare the hypothetical output of a font designed using <a href="http://www.gust.org.pl/projects/e-foundry/metatype1">METATYPE1</a>, where a <a href="http://en.wikipedia.org/wiki/PostScript_fonts#Type_1">Type 1</a> font would be directly generated, versus a font designed using <a href="http://en.wikipedia.org/wiki/METAFONT">METAFONT</a>, where a Type 1 font is generated using <a href="http://lilypond.org/mftrace/">mftrace</a>.</p>
<p>For my experiment, I chose to compare glyphs from the Type 1 version of <a href="http://en.wikipedia.org/wiki/Computer_Modern">Computer Modern</a> maintained by the <a href="http://www.ams.org/">American Mathematical Society</a>, which was presumable crafted by manually tracing the bitmap version and optimizing various aspects by hand, with glyphs generated by mftrace on 3000DPI bitmaps generated from the METAFONT source.  I could imagine that it might be fairer to compare the result of using nearly identical METATYPE1 and METAFONT source to generate the Type 1 glyphs, but then I would be biasing the design process towards the limitations of METATYPE1.  I had considered using the METAFONT source for <a href="http://en.wikipedia.org/wiki/AMS_Euler">AMS Euler</a>, because the source is simply the outline and would be easy to convert to METATYPE1.</p>
<p>I also decided to use glyphs with plenty of curves for the test, as I figure that tracing software can probably do a pretty good job with straight lines.</p>
<p>In any event, I will leave it to you to decide whether you can distinguish which is version is which below.  The order in which the two versions appear differs for each of the three examples below.</p>
<p style="text-align: center;"><a href="http://existentialtype.net/wp-content/uploads/2009/04/qa.png"><img class="alignnone size-full wp-image-309" title="qa" src="http://existentialtype.net/wp-content/uploads/2009/04/qa.png" alt="qa" width="329" height="436" /></a><a href="http://existentialtype.net/wp-content/uploads/2009/04/qb.png"><img class="alignnone size-full wp-image-310" title="qb" src="http://existentialtype.net/wp-content/uploads/2009/04/qb.png" alt="qb" width="326" height="436" /></a></p>
<p style="text-align: center;"><a href="http://existentialtype.net/wp-content/uploads/2009/04/sa.png"><img class="alignnone size-full wp-image-311" title="sa" src="http://existentialtype.net/wp-content/uploads/2009/04/sa.png" alt="sa" width="164" height="226" /></a><a href="http://existentialtype.net/wp-content/uploads/2009/04/sb.png"><img class="alignnone size-full wp-image-312" title="sb" src="http://existentialtype.net/wp-content/uploads/2009/04/sb.png" alt="sb" width="167" height="230" /></a></p>
<p style="text-align: center;"><a href="http://existentialtype.net/wp-content/uploads/2009/04/ampa.png"><img class="alignnone size-full wp-image-307" title="ampa" src="http://existentialtype.net/wp-content/uploads/2009/04/ampa.png" alt="ampa" width="336" height="360" /></a><a href="http://existentialtype.net/wp-content/uploads/2009/04/ampb.png"><img class="alignnone size-full wp-image-308" title="ampb" src="http://existentialtype.net/wp-content/uploads/2009/04/ampb.png" alt="ampb" width="336" height="362" /></a></p>
<p>As you might have guessed, my opinion is that results are so nearly indistinguishable, that given the design limitations of METATYPE1,  it would make much more sense to work with METAFONT and mftrace, and use <a href="http://fontforge.sourceforge.net/">FontForge</a> or a similar tool to add hinting as a postprocessing step.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/04/18/testing-mftrace/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The Controversial Comic Sans</title>
		<link>http://existentialtype.net/2009/04/18/the-controversial-comic-sans/</link>
		<comments>http://existentialtype.net/2009/04/18/the-controversial-comic-sans/#comments</comments>
		<pubDate>Sat, 18 Apr 2009 06:37:55 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[fonts]]></category>
		<category><![CDATA[graphic design]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[comic sans]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=304</guid>
		<description><![CDATA[I figured I would pass along Emily Steel's Wall Street Journal article: Typeface Inspired by Comic Books Has Become a Font of Ill Will.]]></description>
			<content:encoded><![CDATA[<p>I figured I would pass along Emily Steel's Wall Street Journal article: <a href="http://online.wsj.com/article/SB123992364819927171.html">Typeface Inspired by Comic Books Has Become a Font of Ill Will</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/04/18/the-controversial-comic-sans/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>METATYPE1 and meta-fonts</title>
		<link>http://existentialtype.net/2009/04/17/metatype1-and-meta-fonts/</link>
		<comments>http://existentialtype.net/2009/04/17/metatype1-and-meta-fonts/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 22:07:10 +0000</pubDate>
		<dc:creator>washburn</dc:creator>
				<category><![CDATA[fonts]]></category>
		<category><![CDATA[graphic design]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[antykwa toruńska]]></category>
		<category><![CDATA[computer modern]]></category>
		<category><![CDATA[latin modern]]></category>
		<category><![CDATA[meta-font]]></category>
		<category><![CDATA[metafont]]></category>
		<category><![CDATA[metapost]]></category>
		<category><![CDATA[metatype1]]></category>
		<category><![CDATA[mftrace]]></category>
		<category><![CDATA[tracing]]></category>
		<category><![CDATA[type 1]]></category>

		<guid isPermaLink="false">http://existentialtype.net/?p=299</guid>
		<description><![CDATA[I've been spending time lately learning more about working with METATYPE1, mostly for my own projects, but with the eventual hope of writing some tutorials.  While working on one of my running examples, I was encountering some difficulty expressing what I wanted in a reasonably declarative fashion. So I decided to see how it was [...]]]></description>
			<content:encoded><![CDATA[<p>I've been spending time lately learning more about working with <a href="http://www.gust.org.pl/projects/e-foundry/metatype1">METATYPE1</a>, mostly for my own projects, but with the eventual hope of writing some tutorials.  While working on one of my running examples, I was encountering some difficulty expressing what I wanted in a reasonably declarative fashion.  So I decided to see how it was done in <a href="http://www.gust.org.pl/projects/e-foundry/latin-modern">Latin Modern</a>.</p>
<p>I was dismayed to learn that Latin Modern is not a meta-font like <a href="http://en.wikipedia.org/wiki/Computer_Modern">Computer Modern</a>.  Instead the <a href="http://en.wikipedia.org/wiki/PostScript_fonts#Type_1">Type 1</a> versions of Computer Modern (which was developed by either Bluesky or Y&amp;Y) were decompiled into <a href="http://www.tug.org/metapost.html">MetaPost</a> code as raw path outlines.  So at that point all of the useful abstractions in Knuth's original code and specifications have been lost.</p>
<p>The only other major typeface developed in METATYPE1 that I know about, <a href="http://nowacki.strefa.pl/torunska-e.html">Antykwa Toruńska</a>, has no source available and from the description I highly suspect that it was developed by creating raw paths that matched the scanned specimens.  This got me thinking about whether there are any meta-fonts that have been developed in METATYPE1, or even whether Computer Modern might be the only full meta-font family in existence.  I just skimmed through the <a href="http://en.wikipedia.org/wiki/METAFONT">METAFONT</a> sources that are included in <a href="http://www.tug.org/texlive/">TeXLive</a>, but didn't see anything particularly promising yet.</p>
<p>In any event, going back to the original issue, I have been starting to think that maybe the limitations of METATYPE1 are perhaps not worth being able to directly generate Type 1 fonts.  It could be entirely possible that working in METAFONT and using something like <a href="http://lilypond.org/mftrace/">mftrace</a> to generate outline fonts from high-resolution bitmaps will produce results of sufficient quality.  I'm hoping to do some tests to compare the two approaches this weekend.</p>
<p>(It is worth noting, that the comment about METATYPE1 on the mftrace page is slightly incorrect or out of date.  METATYPE1 can handle overlaps, there are just complicated restrictions on how overlapping may occur.  Finding clean approaches to avoid these restrictions was why I became interested in looking at the Latin Modern code to begin with.)</p>
]]></content:encoded>
			<wfw:commentRss>http://existentialtype.net/2009/04/17/metatype1-and-meta-fonts/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

