<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/css" href="/style/rss.css" ?>

<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xml:lang="en-ca">
<channel>
	<title>Michel Fortin Here</title>
	<link>http://www.michelf.com/weblog/</link>
	<description>Thoughts about computers, language, and society by a learned programmer who likes Macs and typography.</description>
	<image>
		<title>Photo of myself</title>
		<url>http://localhost/style/michel.jpg</url>
		<link>http://www.michelf.com/weblog/</link>
	</image>
	<language>en-ca</language>
	<copyright>Copyright © 2010 Michel Fortin</copyright>
	<ttl>120</ttl>
	<lastBuildDate>Fri, 06 Apr 2012 23:45:34 GMT</lastBuildDate>


<item>
<title>Greenwich</title>
<link>http://www.michelf.com/weblog/2012/greenwich/</link>
<guid isPermaLink="false">tag:www.michelf.com,2012-04-06:/weblog/2012/greenwich/</guid>
<description>Nice work from FadingRed. I never liked much Apple’s approach to localization where nib files needs to be manually edited by each translator. Even within Apple, it leads to strange things. Greenwich takes another approach: it loads the nib file and then translate user-visible strings in the created objects using a standard string table.</description>
<pubDate>Fri, 06 Apr 2012 23:44:07 GMT</pubDate>
</item>

<item>
<title>Inflated</title>
<link>http://www.michelf.com/weblog/2012/inflated/</link>
<guid isPermaLink="false">tag:www.michelf.com,2012-03-01:/weblog/2012/inflated/</guid>
<description>I have a 13-inch Unibody MacBook Pro purchased in 2009. This week, the trackpad became very hard to click. In fact, on this computer the trackpad has always been slightly harder to press on the left than on others of the same model, but I wasn’t really concerned. Except this week when it got worse. I opened the bottom panel to see whether I could somehow clean whatever was blocking the trackpad, but without success: the battery covers the area too tightly. But at the same time I understood why the trackpad stopped working.</description>
<pubDate>Fri, 02 Mar 2012 02:00:06 GMT</pubDate>
</item>

<item>
<title>Petition</title>
<link>http://www.michelf.com/weblog/2012/petition/</link>
<guid isPermaLink="false">tag:www.michelf.com,2012-01-22:/weblog/2012/petition</guid>
<description>I got an impression of déjà vu when I found this petition about MPAA bribery on the White House’s website (via Slashdot).</description>
<pubDate>Sun, 22 Jan 2012 22:16:17 GMT</pubDate>
</item>

<item>
<title>What’s important</title>
<link>http://www.michelf.com/weblog/2012/whats-important/</link>
<guid isPermaLink="false">tag:www.michelf.com,2012-01-18:/weblog/2012/whats-important/</guid>
<description>When drafting a law, just like when writing a computer program, we should always keep in mind how it can be abused and what are the consequences of those abuses. Because sooner or later, it will. Usually sooner than later.</description>
<pubDate>Wed, 18 Jan 2012 17:03:52 GMT</pubDate>
</item>

<item>
<title>Introducing MFIndexSetForeach</title>
<link>http://www.michelf.com/weblog/2011/index-set-foreach/</link>
<guid isPermaLink="false">tag:www.michelf.com,2011-12-12:/weblog/2011/index-set-foreach/</guid>
<description>Index sets can be a little annoying in Objective-C. Unlike arrays, sets and dictionaries, you can’t iterate over them using a straightforward for (a in b) loop. That’s because unlike other Objective-C containers, index sets contains integers, not objects. Now, since Mac OS X 10.6 you can use a block to iterate over an index set, but this isn’t always ideal: breaking out of the loop is more complicated, and returning from the block doesn’t return from the outer function. So what can we do better?</description>
<pubDate>Mon, 12 Dec 2011 12:01:29 GMT</pubDate>
</item>


</channel>
</rss>
