mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]:Incorrect parsing of metadata #2618
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#2618
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 @Cotignac on GitHub (Feb 26, 2025).
What happened?
I'm using an application on my Mac called Calibre for adding metadata to my E-books. The reason is that Calibre can download metadata from Google and also Amazon. The result is stored in a catalogue that ABS have access to.
Anyway, a few ABS releases ago that worked good when it comes the parsing of the metadata. But with the latest releases it seems like the handling of paragraphs isn't parsed properly. In the pictures included you can see how the e-book looks like in Calibre and also how it ends up in ABS.
Wouldn't it be great if the parsing of metadata in ABS could store the description as proper HTML and show it the way it was originally written?
What did you expect to happen?
When I try to edit the text it isn't even possible to see where the paragraphs starts and ends so it's hard to correct it. The second of the pictures will show you how i hoped it would look after the import. Preferable with the text in the last paragraph in italic.
Steps to reproduce the issue
Audiobookshelf version
2.19.5
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Edge
Logs
Additional Notes
No response
@Cotignac commented on GitHub (Feb 26, 2025):
I have to add that the metadata is stored in an OPF-file in the same folder as the EPUB-file.
@Cotignac commented on GitHub (Feb 26, 2025):
It wasn't possible to write this as text since it was interpreted so I had to make a screen dump. ;-)
@advplyr commented on GitHub (Feb 27, 2025):
Can you share the opf file? Is it storing HTML in the description?
@Cotignac commented on GitHub (Feb 27, 2025):
metadata (kopia)_opt.txt
This is the file with the extension .txt.
@Cotignac commented on GitHub (Feb 27, 2025):
Just so that you know. I changed the extension to make it possible to upload it. ;-)
@Cotignac commented on GitHub (Apr 28, 2025):
Any idea when you will be able to correct this? Will it ever be corrected...?
@Cotignac commented on GitHub (Jun 2, 2025):
Can you please do something about this?
It's really irritating the way it is now. I've got several hundred e-books and every time I add another book and rescan the library in ABS the manual edited information I have of the other books are destroyed because the metadata is not handled correctly.