More info in my quest to solve the problem with my RSS feed: Following leads from Disscussion boards on radio userland: 1) "Firebird" says the error is on line 163. There's an XML parsing error, but on the radio userland validator it validates just fine. Perhaps an error in the validator is why it hasn't come up as a bug yet for userland. Thanks, Lisa! 2) Jim says it works in Radio and "FeedDemon." And he has seen fishy stuff like that when people post pictures that are too wide. I always take care to trim my photos down to the bare minimum, often making them unreadable, but I hate it that a wide image reformats my nav column due to html scaling. Perhaps I still have some more work to do on this, perhaps others do too. Thanks, Jim! 3) Tried looking in XML Spy to check for well formdedness for the XML. I had to install a new version. Then, I busted out laughing at this dialog box, which is possibly the worst designed dialog ever. I won't put it in-line because I'm superstitious, but here it is. Har har har. When I have a second, I will redesign this for the poor folks over at Altova. Oh, and it says my XML is well formed, but it doesn't like RSS as a schema. This sounds like a problem with XML Spy learning new schemas, so I won't pursue. 4) Last Chance. On to what's going on for line 163, column 1826: In XML Spy they have a cute feature where you can seek ahead to exactly 163/1826, which puts the cursor right before the little square. Yum! That's It' I'll delete and see if it's fixed. Oh, and what possible incentive could people have to check box number three in this dialog? That's all for now, thanks for everyone's help comment []3:16:07 PM trackback [] ![]() |
Every other day or so, my newsreader (still radio, alas) forgets how to process the br tag. Or something. Small bug, but serious problem in that the news is unreadable. This is what it looks like. comment []9:49:06 AM trackback [] ![]() |