<?xml version="1.0" encoding="iso-8859-1"?>
<rdf:RDF
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns="http://purl.org/rss/1.0/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
>

<channel rdf:about="http://ar.ijot.net/blog/rss.rdf">
	<title>ar's weblog</title>
	<link>http://ar.ijot.net/blog/</link>
	<description>visit http://ar.ijot.net/</description>
	<dc:date>2006-06-15T15:08:58Z</dc:date>
	<dc:creator>iJot</dc:creator>
	<items>
		<rdf:Seq>
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-15#u11503788680001/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-15#u11503788680007/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-14#u11502882080001/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-14#u11502871400005/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-14#u11502871400012/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-14#u11502945000016/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-14#u11502871400001/" />
			<rdf:li rdf:resource="http://ar.ijot.net/blog/2006-06-14#u11503745010023/" />
		</rdf:Seq>
	</items>
</channel>

<item rdf:about="http://ar.ijot.net/blog/2006-06-15#u11503788680001/">
	<link>http://ar.ijot.net/blog/2006-06-15#u11503788680001/</link>
	<title>dogfood:encoded</title>
	<description> There's really nothing like eating your own dog food. Since I reluctantly started this blog, I've already fixed a couple of bugs in the PHP back-end code for iJot and isolated another 2 that we're savagely hacking at. Yesterday, Andy - who is blogging using Squib btw - noted that the entity:encoded elements of iJot's rss 1.0 weblog feeds were encoded not once but twice. Oops. Boy do I hate encoding! What's wrong with simple, unaccented, tag devoid, plain English text anyway ? Well, this double trouble is now a thing of the past. Peace to all RSS aggregators...</description>
	<content:encoded> There's really nothing like eating your own dog food. Since I reluctantly started this blog, I've already fixed a couple of bugs in the PHP back-end code for iJot and isolated another 2 that we're savagely hacking at. Yesterday, &lt;a href=&quot;http://thefragens.com/blog/&quot; target=&quot;_blank&quot; title=&quot;andy fragen's squib weblog&quot;&gt;Andy&lt;/a&gt; - who is blogging using &lt;a href=&quot;http://squib.rubyforge.org/&quot; target=&quot;_blank&quot; title=&quot;weblogs managed simply&quot;&gt;Squib&lt;/a&gt; btw - noted that the entity:encoded elements of iJot's rss 1.0 weblog feeds were encoded not once but twice. Oops. Boy do I hate encoding! What's wrong with simple, unaccented, tag devoid, plain English text anyway ? Well, this double trouble is now a thing of the past. Peace to all RSS aggregators...</content:encoded>
	<dc:date>2006-06-15T15:08:58Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-15#u11503788680007/">
	<link>http://ar.ijot.net/blog/2006-06-15#u11503788680007/</link>
	<title>Encoding Redux</title>
	<description> Just when I thought we were finished with encoding woes, I take a look at the activeRoll Gilles has inserted in the right column of his weblog, and lo and behold, it's full of unprintable (?) characters. Gilles, like most of his fellow Quebecois, insists on writing in French, which is plagued with even more accented letters than regular English. The OPML version of Gilles' blogroll is encoded in UTF-8. Gilles' weblog, published with Wordpress, is also encoded in UTF-8. Our own activeRenderer tries to be accomodating with encoding fashions and trends: if the source OPML is encoded in UTF-8, well, let's output the rendered DHTML in the same UTF-8 encoding. Or so we thought. The rendering code on the production server runs under PHP 4, whereas are development server runs PHP 5. Now, of course, the xml parser in PHP 4 handles encoding differently from PHP 5. PHP 4 tries to guess the XML source encoding, and usually fails miserably, defaulting to ISO-8859-1, which renders Gilles' activeRoll unreadable. It looks like I will have to manually detect the source encoding (yikes! regexen to the rescue! :-) and force it down the throat of the XML parser. And to make things worse, with PHP 4, this will only work for UTF-8, US-ASCII and ISO-8859-1. What a way to run a railroad! PHP 5 is marginally better, so we'll migrate the server eventually. Update: I've made a modification to the activeRoll code, so people who are using any of the 3 PHP 4 compatible encodings - including Gilles - should now have properly looking blogrolls.</description>
	<content:encoded> Just when I thought we were finished with encoding woes, I take a look at the activeRoll &lt;a href=&quot;http://gillesenvrac.ca/carnet/&quot; target=&quot;_blank&quot; title=&quot;gilles en vrac&quot;&gt;Gilles&lt;/a&gt; has inserted in the right column of his weblog, and lo and behold, it's full of unprintable (?) characters. Gilles, like most of his fellow Quebecois, insists on writing in French, which is plagued with even more accented letters than regular English. The &lt;a href=&quot;http://gillesenvrac.ca/carnet/opml/opml.xml&quot; target=&quot;_blank&quot;&gt;OPML version&lt;/a&gt; of Gilles' blogroll is encoded in UTF-8. Gilles' &lt;a href=&quot;http://www.dan.co.uk/viewsource/index.php?url=http%3A%2F%2Fgillesenvrac.ca%2Fcarnet%2F&quot; target=&quot;_blank&quot; title=&quot;full http response&quot;&gt;weblog&lt;/a&gt;, published with Wordpress, is also encoded in UTF-8. Our own activeRenderer tries to be accomodating with encoding fashions and trends: if the source OPML is encoded in UTF-8, well, let's output the rendered DHTML in the same UTF-8 encoding. Or so we thought. The rendering code on the production server runs under PHP 4, whereas are development server runs PHP 5. Now, of course, the xml parser in PHP 4 handles encoding differently from PHP 5. PHP 4 tries to guess the XML source encoding, and usually fails miserably, defaulting to ISO-8859-1, which renders Gilles' activeRoll unreadable. It looks like I will have to manually detect the source encoding (yikes! regexen to the rescue! :-) and force it down the throat of the XML parser. And to make things worse, with PHP 4, this will only work for UTF-8, US-ASCII and ISO-8859-1. What a way to run a railroad! PHP 5 is marginally better, so we'll migrate the server eventually. &lt;b&gt;Update&lt;/b&gt;: I've made a modification to the activeRoll code, so people who are using any of the 3 PHP 4 compatible encodings - including Gilles - should now have properly looking blogrolls.</content:encoded>
	<dc:date>2006-06-15T15:08:58Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-14#u11502882080001/">
	<link>http://ar.ijot.net/blog/2006-06-14#u11502882080001/</link>
	<title>activeRenderer</title>
	<description> A few years ago, I provided Radio Userland bloggers a way to publish OPML outlines as regular DHTML Web pages: activeRenderer.  One of activeRenderer's most popular features was the ability to display OPML blogrolls as activeRolls in any Radio weblog's sidebar.</description>
	<content:encoded> A few years ago, I provided &lt;a href=&quot;http://radio.userland.com/&quot; target=&quot;_blank&quot; title=&quot;radio home page&quot;&gt;Radio Userland&lt;/a&gt; bloggers a way to publish OPML outlines as regular DHTML Web pages: &lt;a href=&quot;http://activerenderer.com/&quot; target=&quot;_blank&quot; title=&quot;activeRenderer for Radio&quot;&gt;activeRenderer&lt;/a&gt;.  One of activeRenderer's most popular features was the ability to display OPML blogrolls as activeRolls in any Radio weblog's sidebar.</content:encoded>
	<dc:date>2006-06-15T13:45:07Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-14#u11502871400005/">
	<link>http://ar.ijot.net/blog/2006-06-14#u11502871400005/</link>
	<title>activeRolls</title>
	<description> activeRolls are just like regular blogrolls, with a twist: active outline wedges to uncover underlying levels of information. They provide a dynamic user experience, while preserving screen real-estate and fitting smoothly into the surrounding layout.  While working on the iJot project, I ported most of the Usertalk OPML rendering code to a new Apache/PHP server. So check-out the activeRoll wizard at http://services.activerenderer.com/demo/roll/. It will drive you through the process of creating an activeRoll from any Web accessible OPML file, customizing the roll's style, and inserting the proper code into your weblog's template. Any kind of weblog. No longer limited to Radio. It has been tested with WordPress, Drupal and OPML Editor.</description>
	<content:encoded> activeRolls are just like regular blogrolls, with a twist: active outline wedges to uncover underlying levels of information. They provide a dynamic user experience, while preserving screen real-estate and fitting smoothly into the surrounding layout.  While working on the iJot project, I ported most of the Usertalk OPML rendering code to a new Apache/PHP server. So check-out the activeRoll wizard at &lt;a href=&quot;http://services.activerenderer.com/demo/roll/&quot; target=&quot;_blank&quot; title=&quot;activeRoll wizard&quot;&gt;http://services.activerenderer.com/demo/roll/&lt;/a&gt;. It will drive you through the process of creating an activeRoll from any Web accessible OPML file, customizing the roll's style, and inserting the proper code into your weblog's template. Any kind of weblog. No longer limited to Radio. It has been tested with WordPress, Drupal and OPML Editor.</content:encoded>
	<dc:date>2006-06-15T13:45:07Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-14#u11502871400012/">
	<link>http://ar.ijot.net/blog/2006-06-14#u11502871400012/</link>
	<title>OPML Editor</title>
	<description> With OPML Editor, you will need to update your version to benefit from the new easy stylesheet feature. After restarting, you should: 1. paste the CSS rules defined in the wizard's second step into the new OPML Editor stylesheet (Community / Your OPML Weblog / Open stylesheet menu), 2. paste the links of step 3 in the OPML Editor template (Community / Your OPML Weblog / Open template menu) into the section, *before* the &amp;lt;%stylesheet%&amp;gt; macro, 3. paste the code of step 4 in the template where you want the activeRoll to be displayed.</description>
	<content:encoded> With OPML Editor, you will need to &lt;a href=&quot;http://support.opml.org/2006/06/12#a1184&quot; target=&quot;_blank&quot; title=&quot;OPML Editor easy stylesheets&quot;&gt;update your version&lt;/a&gt; to benefit from the new easy stylesheet feature. After restarting, you should: 1. paste the CSS rules defined in the wizard's second step into the new OPML Editor stylesheet (Community / Your OPML Weblog / Open stylesheet menu), 2. paste the links of step 3 in the OPML Editor template (Community / Your OPML Weblog / Open template menu) into the section, *before* the &amp;lt;%stylesheet%&amp;gt; macro, 3. paste the code of step 4 in the template where you want the activeRoll to be displayed.</content:encoded>
	<dc:date>2006-06-15T13:45:07Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-14#u11502945000016/">
	<link>http://ar.ijot.net/blog/2006-06-14#u11502945000016/</link>
	<title>Grazr</title>
	<description> If you have a little room left in your sidebars, Mike Kowalchik's Grazr provides an extremely clever ipod-like interface to your OPML outlines. A Grazr widget has less styling options than an activeRoll, but delivers a clearer browsing experience for OPML documents that go beyond collection of links.</description>
	<content:encoded> If you have a little room left in your sidebars, Mike Kowalchik's &lt;a href=&quot;http://www.grazr.com/&quot; target=&quot;_blank&quot; title=&quot;grazr home page&quot;&gt;Grazr&lt;/a&gt; provides an extremely clever ipod-like interface to your OPML outlines. A Grazr widget has less styling options than an activeRoll, but delivers a clearer browsing experience for OPML documents that go beyond collection of links.</content:encoded>
	<dc:date>2006-06-15T13:45:07Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-14#u11502871400001/">
	<link>http://ar.ijot.net/blog/2006-06-14#u11502871400001/</link>
	<title>Dog Food</title>
	<description> I have been asked for an OPML weblog to document the resurrection of activeRenderer as a suite of Web services. Well, there's nothing like eating your own... So I've just created a new iJot weblog for this very purpose.</description>
	<content:encoded> I have been asked for an OPML weblog to document the resurrection of activeRenderer as a suite of Web services. Well, there's nothing like eating your own... So I've just created a new &lt;a href=&quot;http://ijot.net/&quot; target=&quot;_blank&quot; title=&quot;iJot's demo site authoring interface&quot;&gt;iJot&lt;/a&gt; weblog for this very purpose.</content:encoded>
	<dc:date>2006-06-15T13:45:07Z</dc:date>
</item>

<item rdf:about="http://ar.ijot.net/blog/2006-06-14#u11503745010023/">
	<link>http://ar.ijot.net/blog/2006-06-14#u11503745010023/</link>
	<title>Thanks Guys</title>
	<description> Thanks to Gwenael for his pioneering work as well as suggesting improvements to the wizard's design, to Dave for enabling style declarations in the OPML Editor, to Donovan for experimenting with the wizard and motivating Dave :-) </description>
	<content:encoded> Thanks to Gwenael for his &lt;a href=&quot;http://radio.weblogs.com/0100306/wizard/activeroll.html&quot; target=&quot;_blank&quot; title=&quot;assistant activeRoll&quot;&gt;pioneering work&lt;/a&gt; as well as suggesting improvements to the wizard's design, to Dave for enabling style declarations in the OPML Editor, to Donovan for experimenting with the wizard and motivating Dave :-) </content:encoded>
	<dc:date>2006-06-15T13:45:07Z</dc:date>
</item>

</rdf:RDF>