From: Tony G. <Ton...@Su...> - 2004-10-06 12:19:00
|
(Replying to part of Stefan's message) Stefan Seefeld <se...@sy...> writes: > Tony Graham wrote: >> I've added a new item (partly so you can see what I've been working on >> when I didn't reply yesterday), but when I generate news.html, all I >> get is an empty <div>. Any ideas? > > Sorry, no. Doing a build locally, I get the content wrapped in > '<div class="rss">'. Is it the same <div> you see, just empty ? That is what I see. I'm using the 2.5 version of the website stylesheets. Looking at the stylesheets and the SourceForge RSS, it appears that the stylesheets are expecting the RSS to use namespaced elements and the SourceForge RSS doesn't. SourceForge claims all sorts of wonderful compatibility and testing for correctness for its RSS feeds, so I don't know who's right and who's wrong about namespaces for RSS. The first step would be to copy the template for the <rss> element into the custom stylesheet and tweak the namespaces on the "select" and "match" attributes to make it work. Second step would be to submit a bug report or enhancement request to the DocBook project. Ideally the templates in the rss.xsl file in the website stylesheets would have "name" attributes so you can call the right template from your customisation even if you're working with not-quite-correct RSS. It might also require that the website templates be more relaxed about namespaces (e.g., use "*:title|title" instead of "rss:title") in their "select" attributes since the structure of the RSS is likely to be correct even when the namespace isn't. >> It shouldn't be a proxy problem, since I'm no longer getting the error >> message that I used to get before I had my proxy set up. > > may be a <xsl:message> put into the xslt file to 'debug' the process > will reveal whether the rss feed could be accessed correctly. You get text in the output HTML when you can't access the URL for the RSS. That's what I used to get before I correctly set my http_proxy environment variable. Regards, Tony. |