Open FishCB opened 3 weeks ago
First, I can confirm that the &
does get read in correctly:
I was able to get it working. I have a Comic Vine library, Rocket Raccoon & Groot (2015)/Rocket Raccoon & Groot #9 (2015).cbz
<?xml version="1.0"?>
<ComicInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Series>Rocket Raccoon & Groot</Series>
<Number>9</Number>
<Volume>2015</Volume>
</ComicInfo>
What happened?
I'm using Kavita to read comics and have a problem with a CBL reading list for "Civil War II" taken from the DieselTech CBL-ReadingLists repository. Kavita does not recognize certain comics in my library, specifically "Rocket Raccoon & Groot," even though the files are present and can be read manually.
It seems the issue is related to an encoding mismatch between the CBL file and the ComicInfo.xml metadata. The CBL file uses
&
to represent the ampersand inRocket Raccoon & Groot,
while the ComicInfo.xml file uses&
.Steps to reproduce:
Expected: Kavita should match the comic and display it correctly in the reading list, regardless of whether the ampersand is encoded as
&
or&
.Current behaviour: Kavita does not recognize the comics from the reading list and marks them as missing. The files can still be accessed and read manually, but they do not appear as available in the reading list.
Here is an example of the relevant sections of the CBL file and ComicInfo.xml: CBL entry:
ComicInfo XML:
Thanks to the Kavita team for the support so far and for looking into this issue!
What did you expect?
Expected: Kavita should match the comic and display it correctly in the reading list, regardless of whether the ampersand is encoded as
&
or&
.Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.3 - Stable
What operating system is Kavita being hosted from?
Linux
If the issue is being seen on Desktop, what OS are you running where you see the issue?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
No response
If the issue is being seen on Mobile, what OS are you running where you see the issue?
None
If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?
No response
Relevant log output
No response
Additional Notes
Aditional info: