D&D Podcast RSS XML error

Post/Author/DateTimePost
#1

lurkerbeneath

Sep 10, 2008 20:40:49
validator.w3.org says:
---
Missing "charset" attribute for "text/xml" document.

The HTTP Content-Type header (text/xml) sent by your web server (Microsoft-IIS/6.0) did not contain a "charset" parameter, but the Content-Type was one of the XML text/* sub-types.

The relevant specification (RFC 3023) specifies a strong default of "us-ascii" for such documents so we will use this value regardless of any encoding you may have indicated elsewhere.

If you would like to use a different encoding, you should arrange to have your server send this new encoding information.

Sorry, I am unable to validate this document because on line 299 it contained one or more bytes that I cannot interpret as us-ascii (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.

The error was: ascii "\x96" does not map to Unicode
---
The offending section of the document is:
---

Episode 14: 4E Announced!
Dungeons & Dragons
In this episode, your hosts � Dave Noonan and Mike Mearls � discuss the major announcement made at Gen Con: 4th Edition!
In this episode, your hosts - Dave Noonan and Mike Mearls � discuss the major announcement made at Gen Con: 4th Edition!

url="http://media.gleemax.com/podcasts/DnD_Episode14.mp3"/>

http://media.gleemax.com/podcasts/DnD_Episode14.mp3

Mon, 20 August 2007 9:30:00 PDT
Games
no
00:38:59


---
Note the invalid-character black-diamond-with-? symbols. iTunes doesn't like this either.
#2

WolfStar76

Sep 11, 2008 10:54:53
validator.w3.org says:
---
Missing "charset" attribute for "text/xml" document.

The HTTP Content-Type header (text/xml) sent by your web server (Microsoft-IIS/6.0) did not contain a "charset" parameter, but the Content-Type was one of the XML text/* sub-types.

The relevant specification (RFC 3023) specifies a strong default of "us-ascii" for such documents so we will use this value regardless of any encoding you may have indicated elsewhere.

If you would like to use a different encoding, you should arrange to have your server send this new encoding information.

Sorry, I am unable to validate this document because on line 299 it contained one or more bytes that I cannot interpret as us-ascii (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.

The error was: ascii "\x96" does not map to Unicode
---
The offending section of the document is:
---

Episode 14: 4E Announced!
Dungeons & Dragons
In this episode, your hosts � Dave Noonan and Mike Mearls � discuss the major announcement made at Gen Con: 4th Edition!
In this episode, your hosts - Dave Noonan and Mike Mearls � discuss the major announcement made at Gen Con: 4th Edition!

url="http://media.gleemax.com/podcasts/DnD_Episode14.mp3"/>

http://media.gleemax.com/podcasts/DnD_Episode14.mp3

Mon, 20 August 2007 9:30:00 PDT
Games
no
00:38:59


---
Note the invalid-character black-diamond-with-? symbols. iTunes doesn't like this either.

Nice analysis.

I'm not entirely sure it will get picked up in the forums, however. Perhaps you could try contacting [email]dndisider@wizards.com[/email] - or PM Solice with this information.

One of the two should be able to get it to the right people.
#3

nmhall

Sep 15, 2008 11:03:23
Any update on the Podcast/rss problem? I tried subscribing this morning again through itunes and it's still coming up busted...
#4

yetirthedark

Sep 16, 2008 21:16:12
feedvalidator.org says there is a mismatch with the file (UTF-8) and the server (ascii).

Glad to see someone else is having issues, this has been driving me crazy.
#5

mudbunny

Sep 16, 2008 21:29:08
I wonder if this is the same thing that is making iTunes not recognize the url of the podcast. If you go directly to the D&D Podcast page, you can get the episodes and manually download them to your iPod.

As for the rss feed, what reader are you using?? The google reader seems to be reading it just fine.