Christopher Hinze has written a great Firefox addon that exports bookmarks to OPML 1.0. Unfortunately, OPML is a bit of an anything-goes specification. So although Hinze’s plugin produces valid OPML, it isn’t the same sort of valid OPML that Google Reader expects. Google Reader, in fact, gags and chokes on Hinze’s OPML, and refuses to import it.

The main problem is that the <outline/> element, the basic hierarchical building block for OPML, will take any attributes. What does that mean in practice? Well, here’s what Hinze’s export produces:

<outline text=”Coding”>
  <outline type=”link” text=”Joel on Software” url=”http://www.joelonsoftware.com/rss.xml” />
</outline>

and here’s the result of Google Reader exporting its own store of RSS bookmarks:

<outline title=”Coding” text=”Coding”>
  <outline text=”drupal.org - Community plumbing”
    title=”drupal.org - Community plumbing” type=”rss”
    xmlUrl=”http://drupal.org/node/feed” htmlUrl=”http://drupal.org”/>
</outline>

To a computer, these are fundamentally two different data formats: the URLs are stored in different attributes, and there are attributes on each that either have different values or are not present on the other. Someone did a DTD for OPML: looking at those two apparently analogous fragments above you have to ask yourself why they bothered.

Help is at hand, though. This sort of problem is bread and butter to XSLT, and here’s an XSL transform for converting Firefox OPML to Google Reader OPML. If you have xsltproc installed on your system, you would type:

xsltproc http://www.jpstacey.info/applications/google/ff2gr_opml.xsl bookmarks.opml > fixed_bookmarks.opml

Or download the XSLT—it’s released under GPL2—and run it locally, changing that URL there to a local file location.

One thing to note: the XSLT will remove an outline wrapped around your bookmarks with title “Sage Feeds” (case-sensitive). So you can export that branch of your bookmarks, and the XSLT will strip the wrapper off and you won’t import a load of bookmarks tagged “Sage Feeds”. If you don’t like this behaviour then either rename your Sage bookmark container, or learn XSLT: it won’t kill you.

There’s a brief README.txt in the zipped archive linked above, but the theme’s main features are:

• XHTML compatible (in core theme files)
• Minimal, semantic markup
• No sidebar
• Excerpts on archive and category pages
• Implicit RSS feeds: the only orange icon is in your browser chrome
• Adaptive top navigation
• Separate pages for archives, categorisation and blogrolls
• Next/previous rel links in header
• Support for special pages e.g. blogroll, tag cloud

The todo list includes:

• Implement my Blogthis! plugin, while trying to keep minimalist
• Unobtrusive hiding of elements, using jQuery
• Improve styling

The theme is in a fairly alpha state. The PHP is fairly straightforward, apart from some neat theme functions, but don’t blame me if everything goes bang.

Alsa seems stable and graphics support is present from installation onwards. Enabling fancier 3D compiz effects requires the nvidia-glx-new package; compiz spots this, however and prompts for installation. All very smooth. Wireless works; my VoIP headset works; but I haven’t yet tested Bluetooth.

The only problem was in upgrading from Gutsy: my previous peregrinations had rendered my hybrid distribution shafted and incapable of upgrade. This isn’t a problem, though, if one has installed the /home directory (and in my case the /music one too) on a separate partition: the Ubuntu Live CD will blat the root partition with Heron, but leave the other partitions alone if you so require. Don’t resize any of your partitions during installation, though, or you’ll lose everything. Everything!

Still, fighting the good green fight can feel pretty lonely, and sometimes you forget not just how many people are on your side in the next office or town, but also of the billions of people who have something to lose to climate change. So as a bit of fun, and to remind ourselves what it’s all about, we’ve recently given the green finger to climate change. Here we are, doing just that:

Want to join in? You can respond to the original YouTube video.

Your mashup is probably legal.
Your mashup is probably sound.
Your mashup is probably legal,
So pass all that data around!

Stuff here
Stuff there
And something mashed up in between (be-tween!)
Stuff here
Stuff there
And something mashed up in between

Your mashup is probably legal;
You could monetize it as well!
But though I contend it’s all legal,
Remember I-A-N-A-L!

[Repeat chorus]

But what makes it all far, far worse is that IE6 and IE7 can sometimes produce error messages which, as is usual for those browsers, contain no useful information whatsoever.

Here’s a recent example:

Line: 64432871
Char: 2
Error: Expected identifier, string or number

See that impossibly high line number? That’s a result of the parser being struck soundly on the head by the syntax error, and consequently dribbling its way past the end of the Javascript file. IE’s incomprehensible “English” error message conspires with circumstance to make the whole report of no help at all.

Something like JSLint, on the other hand, is of tremendous help, and we’ll be running as much Javascript through it as possible in future. JSLint is just as unforgiving, but as it’s reliably unforgiving and incredibly communicative with it then that’s a bonus rather than a detriment.

It’s sometimes a little too strict to be useful, complaining about implicit global variables (even when that variable is called window). My suggestion is to ignore those reports, though; but watch those commas!

The session I compèred went reasonably well: I can’t say my elegant prose exactly sparkled, and I occasionally found myself getting into the subjects being discussed so much that I forgot to flash the “X minutes left” warning signs. With that in mind, thanks are due to speakers Ben, Steven, Roo and Nick for both their talks and their patience. Hopefully there’ll be some area for speakers to upload their slides etc. soon, so I can link their names through to it when that happens.

Entrance is only a fiver and the schedule looks great. Like its predecessors (OT2005 and NotCon2004) OT2008 is “informal, low-cost”, but the slant is more towards using technology to promote and enable low-carbon and sustainable living.

I’ve also been roped into compèring one of the sessions. It’ll probably be one I know nothing about (just from looking at the running order), but the beauty about compèring as opposed to actually chairing is that you can be completely ignorant of the subject matter and nobody might ever realise. Should discussion begin to flag, I may do a little dance. That’ll be worth the entrance fee alone.

Drupal.org have produced a Licensing FAQ to explain some of the subtler aspects of licensing under the GPL. The questions themselves are Drupal-oriented, but the FAQ itself has been prepared by the SFLC, an independent body, so the answers are broader than that.

I’ve noticed from the slightly confused sidelines that Drupalers have been niggling away at these issues for ages. Their heated exchanges and occasional quarrels are the fuel that has kept this wagon moving, and they’ve finally rolled it into town with a GPL-in-practice primer that’s worth reading, whatever you’re working on, and especially if you’re integrating with web services or third-party libraries. Well done to all involved.