mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Some podcasts are showing incorrect characters #943
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#943
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @adocampo on GitHub (Feb 7, 2023).
Describe the issue
I've just several podcasts and on some of them (2 at the moment) on some letters with accents (i.e.: á, à, é, è, í, ò, ó and ú) and other non-English letters like ç, all those are downloaded and shown as � both in audiobookshelf and file system. Other Spanish and Catalan podcasts are downloading and showing the text just fine, the problem is just with those two
The RSS are : https://dinamics.ccma.cat/public/podcast/catradio/xml/9/5/podprograma1859.xml (another from the same source, with the same issues: http://dinamics.ccma.cat/public/podcast/catradio/xml/4/4/podprograma1744.xml) and https://www.ivoox.com/feed_fg_f1455079_filtro_1.xml
As you can see, the origin has the proper characters
But when downloaded, they all are shown like �
or the one from ivoox, with this
&#XXX;encoding, in green , some entries with the proper encoding, weird...I've noticed they are shown wrong just adding the show
By renaming the files at filesystem level, they show properly on ABS, and editing manually the details on ABS and saving them, also shows the texts just fine, the problem is only when downloading new episodes.
Steps to reproduce the issue
Audiobookshelf version
v2.2.12
How are you running audiobookshelf?
Docker
@advplyr commented on GitHub (Feb 11, 2023):
I was only able to see mojibake with the first RSS feed.
With https://www.ivoox.com/feed_fg_f1455079_filtro_1.xml this was coming back with utf-8 encoding.
This one is not returning anything http://dinamics.ccma.cat/public/podcast/catradio/xml/4/4/podprograma1744.xml
The solution I implemented relies on the content-type header in the response to include charset like
charset=iso-8859-1@advplyr commented on GitHub (Feb 12, 2023):
Fixed in v2.2.15
@nation-wide commented on GitHub (Oct 30, 2024):
Is it possible to have this same fix for .nfo files parser? If .nfo file's charset is iso-8859-1 it will show the audiobook's "ä, å, ö" etc. as �.