Hi, for the past couple months, I have several feeds where accents (I’m french speaking) are not displayed correctly. It used to work fine before, and still works in other RSS aggregators that I tried. So it seems a problem on Newsblur side.
Here is one example : https://www.journaldugeek.com/category/science/feed/
Can you have a look?
Thanks!!!
Sébastien
I forgot to mention, I use the TEXT view to get the full content.
I’m using Newsblur web with Edge v144.0.3719.92 on W11 at work. That’s where I have the problem. All extensions are disabled. (On Mac and iOS I use 3rd party apps that don’t show the issue)
Here is what I see using the TEXT view :
The posts before November 21st 17:02 don’t have the issue, all posts since then look like the screenshot with no accents inside the text (title is fine).
Tried with Firefox, same issue but seems more random, some news have accents, others don’t.
Ohhh, looks like that’s cached text on old stories. Sorry but the fix isn’t retroactive. Any story after January 9th should work fine. I can clear that particular feed’s cache if you like (and I just did, so now those stories should work retroactively) but there may be other feeds that need retroactive rewriting. If so, let me know and I can gladly clear their cache.
Sorry for the delay, I had to make sure… the problem is indeed solved!
I had several feeds linked to that particular website and they all work fine now. Not sure I understood your explanation of the problem since all new articles had the same problem for me, so I don’t see how it’s related to cached articles before January 9th. Articles past that date still had the problem until you did your magic trick 
Thanks again!
Just noticed that the STORY view has the accent problem on the feed. I don’t use it since the TEXT view works so well. You might have a look since someone else might affected.
Thanks for reporting this! Just landed the same fix for the Story view as well. The root cause was servers not specifying charset in their HTTP headers, which caused our fetcher to assume ISO-8859-1 instead of UTF-8. Now deployed. And I just verified all the stories are now fixed.
Ha thanks for the explanation! I can confirm it all works fine now 
