-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numbers in the series name recognized as chapter number if no chapter number in comicinfo.xml #2908
Comments
Is there anything I can help with to get this out of the triage stage? |
I need community help with this because partial ComicInfo is a feature many people need. You shouldn't have to tag everything perfectly to correct one issue. The problem comes from the filename parser, but it's not something that can be fixed per-se. My idea would be to use a unique symbol that would never be real that Kavita can read and ignore said field. |
@CtrlAltDefeat94 can you try for now as a temp workaround to tag the Number field as |
I'm all in for a special value in comicinfo. So far Ive been tagging these as chapter 0 as a legacy measure. |
Here is the situation with filename parsing: These are both real titles. The first is the Re:ZERO Chapter 4 case, where Chapter 4 is part of the series name. Whereas From a filename parsing standpoint, there is no way to know the difference so there is no way to write a rule to accurately identify. The latter is the most common. So Using a unique key, like |
Is it not possible to let the user manually override the parser? |
@SleepingPanda That is what tagging your files with metadata is doing. It's telling Kavita exactly what to take it as. |
Right but tagging potentially hundreds of files may not always be a reasonable option. I'm asking if there is no way to allow that from within Kavita itself. |
I don't think so. I did a proof of concept to allow a library where the user defines the Regex, but it wouldn't necessarily solve this problem and was quite complex to support (and likely will be underused due to the complexities of parsing--the reason we have this issue to begin with). Just allowing loose filenames is not something I want the software to support nor something I want to be restricted to design around for future UX work. |
There's a surprisingly wide variety of series with numbers in their names and I don't think tagging our files with a Kavita-specific symbol should be the long-term solution. There are use cases like mine (and a friend's) where files can't be modified for example. |
I would find a setting useful to disable filename parsing for any file that contains a comicinfo.xml. |
I would be open to trying something like this. If you could open a FR and link back to this thread, that would help ensure it doesn't get lost. |
What happened?
When the series name in the title contains a number such as
Fairy Tail: 100 Years Quest Vol. 1: New Start, New Quest
, this number is parsed as a chapter number. All volumes in this series are added for both their Volume number and Chapter 100.What did you expect?
If a cbz file has a comicinfo.xml and does not contain a Chapter tag, it should not add a chapter number.
Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.1 - Stable
What operating system is Kavita being hosted from?
Docker (Dockerhub Container)
If the issue is being seen on Desktop, what OS are you running where you see the issue?
None
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
No response
The text was updated successfully, but these errors were encountered: