In my experience, the problem is in many cases in the character encoding used in the feed. If the feed is encoded using ISO-8859-1 encoding (which is what CNN top stories appears to use), and you are trying to read it using the default UTF-8 encoding some symbols will come as invalid and break the parser. The only viable solution is to manually detect the encoding before trying to parse and then construct the input stream given to the parser with the correct encoding. This is what I end up doing for BeyondPod in both Windows Mobile and Android platforms and this solved large set of parsing issues. Welcome to the bizarre world of RSS parsing.
Stefan On Mar 1, 10:03 am, grennis <[email protected]> wrote: > OK, thanks all. I didn't realize the problem was as pervasive as it > is. I'm presenting a limited set of feeds so I'm hoping the scrub > approach will work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
