Problem with Ow.ly when URL contains ampersands

Hello,
We've found that your feed is outputting some bad data. Here's an example of the data we get. This is one of the feed posts:

Apple iPad al servizio del fotografo
http://www.osservatoriodigitale.it/in...

Redazione
Thu, 28 Jan 2010 14:25:49 +0100
http://www.osservatoriodigitale.it/in...

You'll see that in the link field the "&" in the url has been incorrectly double-encoded. They all show as "&" instead of the correct "&amp" value that is common. We do a single-pass decode when we parse the feed which works for most urls. But for your feed we're left with "&amp" in the url.

Typically, "&" characters should ever need to be double-encoded. This is probably due to some sort of bad setting or a bug in the feed generating software used by the website.

Oops. The browser tried to render the xml code I pasted in. I'll try to paste it in again:

<item>
<title>Apple iPad al servizio del fotografo</title>
<link>http://www.osservatoriodigitale.it/in...;
<description></description>
<author>Redazione</author>
<pubDate>Thu, 28 Jan 2010 14:25:49 +0100</pubDate>
<guid>http://www.osservatoriodigitale.it/in...;
</item>

Thanks Michael, but I think that Ow.ly should not delete the second semicolon. It correctly decodes the first five digits (let me space them so the browser doesn't render them) "& a m p ;" but as I see it, if it chooses not to decode the remainder of the string, then why it removes the last semicolon? If it didn't, browsers could resolve the URL correctly and I'd be a happy man ;-)

BTW the URL string was produced by the PHP standard function htmlspecialchars(), so I don't have much choice here :-)
It might also be interesting to know that the W3C feed validator doesn't warn about it. I have also tried other shortener services: Tiny.url produces a URL with "& a m p ;" (which the browser gladly accepts), Bit.ly produces "&". But I'd really like to stay with Hootsuite/Ow.ly...