Chris and Mark, Thank you for replies. I agree of course with what Chris noted "How they are displayed depends entirely on the client application."
As I mentioned, the latest versions of IE and Firefox have built in capabilities to display RSS feeds with some minimal formatting and this works fine with my TG-generated RSS 2.0 feeds. However, there does seem to be some difference in how less-than-latest versions of IE and Firefox react to a URL for TG-generated RSS 2.0 feeds (which result in a "Save As" dialog) as compared to other feeds (which are displayed in raw XML format in the browser, tags and all). To me, the latter approach of displaying XML in browser is in two ways preferable to having the "Save As"dialog displayed: (1.) user is given some quick and easy visual feedback about what the data is, even though it's not in a pretty form, and (2.) the feed URL is then conveniently sitting in the browser's input box for easy copy/paste or even mouse-dragging into an RSS feed reader. The "Save As" dialog is much less convenient because no quick easy visual feedback is provided (would have to save to disk then open with text editor) and no easy access to the URL is provided (although a smart Firefox user will right-click and "Copy Link Location", or in IE it's not quite as easy but a user can right-click for "Properties" and then copy/paste the URL). Perhaps I'd need to video myself trying to do all this to sufficiently convey the user experiences I'm talking about! So getting back to the point that the client/browser is the proper target of my complaint, not TG, yes I agree but still for some reason it seems the "Save As" happens for TG-generated feeds but not other people's RSS feed URLs that I click on - those are displayed as XML in the browser. So there seems to be some difference related to TG. Speaking of which, there is another *possibly* TG-related issue I'm having with my RSS 2.0 feeds: Google Reader and Bloglines recognize them fine, but some other readers such as My Yahoo and others refuse to do so, claiming it's not recognizable as an RSS feed. Last month, I was also not able to get Google and Bloglines to recognize my feeds but that turned out to be because I was foolishly using a redirect before I knew URL keywords can be passed to get_feed_data. But now it seems Google, Bloglines, latest version IE, and latest version Firefox all recognize my TG-generated RSS as good, but Yahoo and some others won't. I realize this is a separate issue and I should submit a different issue about it, but I mention it here because maybe there's some relation to the "Save As" behavior, in that perhaps some slight aspect of TG-generated RSS causes some clients to not recognize it as such. Wonder if anyone else has observed things like this? On Jun 23, 7:24 am, Christopher Arndt <[EMAIL PROTECTED]> wrote: > buffalob schrieb: > > > Thanks Chris. > > I understand that very well, but some users of my feeds might want > > direct visual display before deciding whether to subscribe to it. > > That still makes no sense to me. RSS feeds have no "visual" appearance, > they're just data formatted in XML. How they are displayed depends > entirely on the client application. > > If you mean that you want users to give an idea of the *data* contained > in the feed, provide an alternate version of the data, that is viewable > (via a different template). For example, in a Blog application, the > viewable version would be the blog roll or front page. > > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
