You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Suwayomi to host a local library, the detection of chapters can be temperamental and the documentation provided does not entirely adequately explain how filenames are parsed in plain language.
At present, chapters released with their year in the filename will see all chapters from that same year marked as read, as the year is being detected as "chapter" in lieu of "Ch01" or "v01" for volume releases. This also affects next chapter navigation, as the user will be shunted forward multiple volumes in some cases.
Pattern matching for "Volume XX" "vXX" "ChXXXX" "Chapter XXXX" would be ideal to take priority over any loose number deteced. And if possible, flagging vXXX or Volume should be able to prioritize those volumes of collected chapters over loose chapters.
Finally, some escape characters or patterns. Many files are tagged with groups, quality, etc, in parenthesis. This is the most obvious choice from an armchair perspective, so adding () to be skipped seems logical to filter these. (2024) is not chapter 2024 clearly.
Unsure of the burden adding this to the local chapter scanning may have, but it would be an incredibly QoL improvement for those with local libraries to have them sort correctly.
The text was updated successfully, but these errors were encountered:
jedinjapan
changed the title
[Chapter Numbering] Explicit Rules for Local Sources Chapter Detection - Escape/Exclude Years and Quality Info
[Feature Request] Chapter Numbering - Explicit Rules for Local Sources Chapter Detection - Escape/Exclude Years and Quality Info
Dec 16, 2024
If Suwayomi could offer even the option for a user-inputted regex value it would still be an excellent option to have.
The use case between Mihon and Suwayomi is just different enough this begins to really matter. Hosting ones own collection from a home server for your devices to browse means having it read your filenames is critical, and right now what is getting picked up on is somewhat unclear.
When using Suwayomi to host a local library, the detection of chapters can be temperamental and the documentation provided does not entirely adequately explain how filenames are parsed in plain language.
At present, chapters released with their year in the filename will see all chapters from that same year marked as read, as the year is being detected as "chapter" in lieu of "Ch01" or "v01" for volume releases. This also affects next chapter navigation, as the user will be shunted forward multiple volumes in some cases.
Pattern matching for "Volume XX" "vXX" "ChXXXX" "Chapter XXXX" would be ideal to take priority over any loose number deteced. And if possible, flagging vXXX or Volume should be able to prioritize those volumes of collected chapters over loose chapters.
Finally, some escape characters or patterns. Many files are tagged with groups, quality, etc, in parenthesis. This is the most obvious choice from an armchair perspective, so adding () to be skipped seems logical to filter these. (2024) is not chapter 2024 clearly.
Unsure of the burden adding this to the local chapter scanning may have, but it would be an incredibly QoL improvement for those with local libraries to have them sort correctly.
The text was updated successfully, but these errors were encountered: