Try this URL and you'll see
Might be connected with previously reported UTF-8
problem, although the feed doesn't seem to have any
actual non-ASCI chars.
Additional thing, and the reason why I tried this
URL, is that the reader would need to provide access
to all tags contained in the //item tag. The reason
is that for feeds like this one, these tags usually
contain some info that the user needs. In this case
the //item/guid contains the URL to the actual
Log in to post a comment.