I have to say... I'm much more of a "practicalist". I'd say that in the Real World, the
primary use of OPML files, in just about every application that supports them, is to interchange podcast data with iTunes. So, saying that Apple doesn't support the standard properly, is completely irrelevant from an end-user's perspective. Therefore, the "standard" (little "s") is whatever Apple decides to do, and the Standard (big "s") be damned. Facts on the ground and all that.
Now, granted, they didn't define the OPML system. But they also aren't the ones who started using them for exchanging podcast data. That was added well after the practice was implemented by 3rd Parties. So, assuming that iTunes' OPML files are similarly ugly, is probably related to whomever originally did the work, and they were stuck with what had become "common practice" by the time they implemented it.
Now, it could be that just stupid iCatcher's OPML files are ugly. That's possible. In that case, I'd say it isn't worth fixing just for me. That's fine. I did notice before when iTunes imports these OPML files, it actually shows those same %20 characters for a split second, but then it "fixes" them. In any case, it works right. Here's the same feeds exported as an OPML from iTunes:
http://glynor.com/temp/iTunes_Podcasts.opml.zipIn any case,
the guy who develops iCatcher (which is a one-man shop, I believe) would probably be open to correcting problems. I've emailed him before and he was helpful and friendly. I'd guess that as long as it doesn't break interchange with iTunes and the other major podcast catchers in the App store (which would defeat the main point of his support for the format) I bet he'd be open to fixing it.
And... As far as this:
As for making MC 'work around it'.... DON'T.
I mean... Whatever. I understand where you're coming from, but that essentially would say to me:
Do not use MC for podcast support because it doesn't interchange with other common applications well. (Again, assuming that iTunes' files are similarly broken, which might not be a good assumption.)
I'm a practicalist.
Obey standards when you can, but don't let it get in the way of your real work, especially when the standards are so loosely followed that you'd be alone in the wilderness.