While
merlyn's solution works well, I prefer a more
XML native approach. The
RDF file should be valid XML, in which case you only need apply an
XSL Transformation to the file once you have it, to get valid XHTML, WML or whatever out.
This is the basis of XML::RSS::Tools, a module I've been developing. Here is an example of the usage:
#!/usr/bin/perl -w
use strict;
use XML::RSS::Tools;
my $site = shift;
my $xsl = shift;
my $rss = XML::RSS::Tools->new;
$rss->rss_uri($site) or die $rss->as_string('error');
$rss->xsl_file($xsl) or die $rss->as_string('error');
if ($rss->transform) { print $rss->as_string };
There are however problems:
- XML::RSS module has some defects
- Perl before 5.7.x isn't exactly the best for working with Unicode
- RSS feeds often are not valid XML - How do I clean RSS feeds to make them usable?
- My module still has bugs in... :-(
- UPDATE: Versions later than 0.05 have less bugs, and partially get round the defect in XML::RSS and dirty feeds
My humble 2p
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.