-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make Volume tag accept decimals #185
Comments
Related: #174 |
Technically float values are not supported by comicinfo schema 🤔 |
Never saw your reply, sorry for the late response. I have some manga that releases bonus volumes bundled with limited edition of the physical book, which are commonly labelled as vol XX.5 as they are intended to be read after said volume. Currently, specials can cover for this in a limited manner since you have to switch tabs and remember where you're supposed to read the .5 volume |
Perhaps we can raise a spec change request supporting float volumes and then move forward with implementation, regardless of if it merges or not. @Roshri would you be able to provide some official Volume x.5 samples? |
I can email you the .cbz for vol 10.5 of the series I pictured above. It's a small ilustration book with a short story, it came bundled with vol 10 |
Roshri, would you be willing to open a spec enhancement here? I'm not saying it will get approved, but it is the first step to allowing MM to change against the spec (like we did with LocalizedSeries in MM/Kavita) |
Just following up @Roshri (or anyone interested), nothing has been opened requesting this on the spec. |
I forgot, I'm on vacation right now, I'll open it when I come back! Thanks for the reminder edit: just created the issue |
Is your feature request related to a problem? Please describe.
I have some volumes for specific manga that have decimal on them, and Manga Manager doesn't accept the dot (.) separator to represent it on the volume tag.
Example of one series
Describe the solution you'd like
Ideally, I'd like to have it so I can have the decimal in between integers, so 10.5 would be between 10 and 11 when displaying in Kavita. (And not whatever fuckery w10 does where it shows the decimal first lol)
The text was updated successfully, but these errors were encountered: