-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot parse a malformed feed #91
Comments
Hey. Not sure how to solve this. This is the error we get:
The problematic String seems to be this:
I assume that the � marks that this was maybe a cut multi byte character? There are some workarounds, but they involve setting the encoding of that string of the RSS feed with something like https://ruby-doc.org/core-2.7.0/String.html#method-i-encode or guessing the encoding with a gem. I'd be very worried about breaking a lot of things with that. In general I agree that Pipes should just handle this feed somehow, but this is such a wide field of potential issues that hoping the input feed gets fixed seems like a better option to me. But input on how to safely solve this is welcome, I certainly might be wrong here. |
Thank you for looking into it.
Yes, the original title says 31日発売.
Alright. This issue is too specific to worry too much about it. FeedRinse has some internal filters too, and I can use them to remove problematic posts in case they don't fix their parser soon. |
@onli What about this other case? Something is causing one my subscriptions to add invalid XML entities to item titles. I believe it's always a series of Removing the invalid character entities from the code at the moment the feed is downloaded would be enough to fix it. I can't do it with a
|
This feed currently contains an encoding issue and Pipes cannot parse it: http://feedrinse.com/services/channel/?chanurl=882eadeaf9ef2636f65d656793114983 .
I've reported this to Feed Rinse, but could you take a look to see if you can find a workaround? SimplePie can handle it and just replaces the broken character with a normal question mark: https://www.simplepie.org/demo/?feed=http%3A%2F%2Ffeedrinse.com%2Fservices%2Fchannel%2F%3Fchanurl%3D882eadeaf9ef2636f65d656793114983
The text was updated successfully, but these errors were encountered: