<?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>ChrisAcheson.net &#187; ubuntu</title>
	<atom:link href="http://chrisacheson.net/blog/tag/ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisacheson.net/blog</link>
	<description></description>
	<lastBuildDate>Fri, 20 Apr 2012 14:02:47 +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>How to get ProFont working in Ubuntu</title>
		<link>http://chrisacheson.net/blog/2009/03/21/how-to-get-profont-working-in-ubuntu/</link>
		<comments>http://chrisacheson.net/blog/2009/03/21/how-to-get-profont-working-in-ubuntu/#comments</comments>
		<pubDate>Sat, 21 Mar 2009 07:16:21 +0000</pubDate>
		<dc:creator>Chris Acheson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://chrisacheson.net/blog/?p=8</guid>
		<description><![CDATA[At the suggestion of a friend, I&#8217;ve recently started using a font called &#8220;ProFont&#8221; for my programming and other terminal-related activities.  It&#8217;s quite nice, and designed to be readable at small sizes.  I use it at 8 point: I don&#8217;t actually use 80&#215;24 anymore, but you get the idea. It didn&#8217;t immediately work when I [...]]]></description>
			<content:encoded><![CDATA[<p>At the suggestion of a friend, I&#8217;ve recently started using a font called <a href="http://www.tobias-jung.de/seekingprofont/">&#8220;ProFont&#8221;</a> for my programming and other terminal-related activities.  It&#8217;s quite nice, and designed to be readable at small sizes.  I use it at 8 point:</p>
<div id="attachment_10" class="wp-caption aligncenter" style="width: 502px"><img class="size-full wp-image-10" title="ProFont Konsole" src="http://chrisacheson.net/blog/wp-content/uploads/2009/03/profont_konsole.png" alt="8 point ProFont in an 80x24 terminal" width="492" height="327" /><p class="wp-caption-text">8 point ProFont in an 80x24 terminal</p></div>
<p>I don&#8217;t actually use 80&#215;24 anymore, but you get the idea.</p>
<p>It didn&#8217;t immediately work when I installed it on my main machine (which runs Kubuntu), and it took some digging to figure out why.  It turns out that fonts on modern Linux machines are handled by a horrible chimera.  There&#8217;s the new font system, &#8220;fontconfig&#8221;, as well as the old &#8220;core X font subsystem&#8221;.  The instructions that I had found online installed ProFont into the old font system, but not into the new one.  I also tried using the GUI font configuration tool provided by KDE, but it did nothing.</p>
<p>After much searching and frustration, I discovered that Ubuntu and its variants have fontconfig configured to not use bitmap fonts by default.  ProFont is a bitmap font, and such fonts are usually used by old X applications that use the old font system.  The reason for this configuration is that a lot of the bitmap fonts have the same name as other fonts on your system, and if they&#8217;re enabled they may in some instances end up being used instead of the typically better-looking vector fonts that you usually see.</p>
<p>In order to get ProFont working, you&#8217;ll need to add an exception to your fontconfig configuration.  I suggest editing the <kbd>~/.fonts.conf</kbd> file, which contains user-specific options.  Here&#8217;s mine, with the part that I added in bold:<span id="more-8"></span></p>
<blockquote>
<pre>&lt;?xml version="1.0"?&gt;&lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
&lt;fontconfig&gt;
 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="rgba" &gt;
   &lt;const&gt;none&lt;/const&gt;
  &lt;/edit&gt;
 &lt;/match&gt;
 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="hinting" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;
 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="hintstyle" &gt;
   &lt;const&gt;hintfull&lt;/const&gt;
  &lt;/edit&gt;
 &lt;/match&gt;
 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="antialias" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;
 <strong>&lt;selectfont&gt;
  &lt;acceptfont&gt;
   &lt;pattern&gt;
    &lt;patelt name="family"&gt;&lt;string&gt;ProFont&lt;/string&gt;&lt;/patelt&gt;
   &lt;/pattern&gt;
  &lt;/acceptfont&gt;
 &lt;/selectfont&gt;</strong>
&lt;/fontconfig&gt;</pre>
</blockquote>
<p>If <kbd>~/.fonts.conf</kbd> doesn&#8217;t exist, just create it with your a text editor and copy the following into it:</p>
<blockquote>
<pre>&lt;?xml version="1.0"?&gt;&lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
&lt;fontconfig&gt;
 &lt;selectfont&gt;
  &lt;acceptfont&gt;
   &lt;pattern&gt;
    &lt;patelt name="family"&gt;&lt;string&gt;ProFont&lt;/string&gt;&lt;/patelt&gt;
   &lt;/pattern&gt;
  &lt;/acceptfont&gt;
 &lt;/selectfont&gt;
&lt;/fontconfig&gt;</pre>
</blockquote>
<p>Once that&#8217;s done, download ProFont for Linux from <a href="http://www.tobias-jung.de/seekingprofont/">Tobias Jung&#8217;s ProFont page</a>, extract the tarball, and copy the .pcf files inside into your <kbd>~/.fonts/</kbd> directory (create it first if it doesn&#8217;t exist).  On the command line, run:</p>
<blockquote><p><kbd>fc-cache -fv</kbd></p></blockquote>
<p>This will force fontconfig to rebuild the font cache, and load ProFont in the process.  Now restart any running apps that you want to use ProFont in, and you should be good to go.</p>
]]></content:encoded>
			<wfw:commentRss>http://chrisacheson.net/blog/2009/03/21/how-to-get-profont-working-in-ubuntu/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

