Open gnatbandanna opened 18 hours ago
Same as https://github.com/FreshRSS/FreshRSS/issues/754 , which was fixed by https://github.com/FreshRSS/FreshRSS/pull/813 and sent upstream as https://github.com/simplepie/simplepie/pull/400 but then reverted upstream as https://github.com/simplepie/simplepie/pull/433 , which made that we lost the fix during the big SimplePie refactoring https://github.com/FreshRSS/FreshRSS/pull/4374
However, the fix was probably not correct for all cases, so should be re-evaluated. https://validator.w3.org/feed/docs/warning/ContainsHTML.html https://www.rssboard.org/rss-profile#data-types-characterdata
In any case, the feed is not following the recommendations https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Flemmy.ml%2Ffeeds%2Fc%2Fprivacy.xml%3Fsort%3DActive
Looking at this specific feed and bug, the original source is:
<title>Polling the group: what do y&#x27;all know about the Orion browser from Kagi?</title>
(This means a double XML encoding)
That definitely shouldn't be supported by default. ^_^
Indeed, I have been looking at what could / should be done, and I do not believe this invalid feed can be be supported without breaking legitimate use cases in other valid feeds.
Valid representations should be:
<title>Polling the group: what do y'all know about the Orion browser from Kagi?</title>
<title>Polling the group: what do y'all know about the Orion browser from Kagi?</title>
The bug should be reported to https://github.com/LemmyNet/lemmy/issues
The bug should be reported to https://github.com/LemmyNet/lemmy/issues
Will do, thanks!!
Describe the bug
I believe this to be an issue with Edge (1.24.x worked fine) and
Lemmy
RSS feeds (probably others). Lemmy feeds are coming across as:Which is then just displayed as is without translating to something more readable, such as
'
:I suppose that's fine, but this wasn't an issue with the 1.24.x branch. The titles were properly parsed and displayed.
To Reproduce
Presumably add a feed like the one above and then look at the title with any client/browser to see the unicode jibberish.
Expected behavior
I'd expect something like
[...] what do y'all know [...]
FreshRSS version
1.25.0-dev
Environment information
Additional context
No response