daiz / manga-naming-scheme Goto Github PK
View Code? Open in Web Editor NEWManga Filename Scheme
Manga Filename Scheme
Hey there, Daiz! So, I ran into another issue recently... For anthology manga such as Robot, I'm having trouble figuring out what is the best way to sort stuff...
Most of what these anthologies publish are one-shots, but especially in the case of Robot, it seems like most users still have a desire to sort each volume in the order the chapters were published, despite the chapters being unrelated.
Now, most users have adopted a chapter numbering system that works per-volume... (for example, volume 1 might have chapters 1-8, and then, volume 2 would have a separate batch of chapters, also numbered 1-8).
However, this style doesn't seem to work for our naming scheme since the chapter number comes first, leaving things to be sorted as following:
Robot - 001 (v01) [Oneshot] [Group Name]
Robot - 001 (v02) [Oneshot] [Group Name]
Robot - 001 (v03) [Oneshot] [Group Name]
Robot - 001 (v04) [Oneshot] [Group Name]
Robot - 002 (v01) [Oneshot] [Group Name]
Robot - 002 (v02) [Oneshot] [Group Name]
and so on...
So, what is the alternative?
I propose perhaps adopting a naming scheme specifically for anthologies that gets rid of chapter numbering, like so:
Robot - (v01x1) [Oneshot] [Extra Information] [Group Name]
Robot - (v01x2) [Oneshot] [Extra Information] [Group Name]
Robot - (v01x3) [Oneshot] [Extra Information] [Group Name]
I suppose we could possibly still go with the "000" method used for other one-shots, and have it be like this:
Robot - 000 (v01x1) [Oneshot] [Extra Information] [Group Name]
Robot - 000 (v01x2) [Oneshot] [Extra Information] [Group Name]
Robot - 000 (v01x3) [Oneshot] [Extra Information] [Group Name]
Although, in my opinion, that's just three extra unneeded characters.
Another good idea would be to have the chapter title in the file name... seeing as they are one-shots, it should be in there somewhere. I propose something like this:
Robot - 000 (v01x1) - Chapter Title [Oneshot] [Extra Information] [Group Name]
Robot - 000 (v01x2) - Chapter Title [Oneshot] [Extra Information] [Group Name]
Robot - 000 (v01x3) - Chapter Title [Oneshot] [Extra Information] [Group Name]
Edit: Another thing I ran into... for oneshots where the source isn't from a magazine, the web, or a numbered volume... should I just use (vol) instead? There's many anthology books out there that collect one-shots from magazines, but since the raws came from a volume I feel like I should still list it as such. What do you think?
Just curious how manga with chapters that start at 0 (whether it be a prologue or just the first normal chapter) should be handled. Should we follow each mangas original system, having some starting at c000 and some starting with c001 (especially since the chapter numbers may actually listed inside the manga itself) or should we change everything to start at either c000 or c001?
Same goes for page numbers, those are usually all over the place in various downloaded rips. Some Scanlators choosing to start at 0, some start at 1, some have things like pages listed 01-25 with a page labeled 001 to ensure its at the start. Some magazine scans start at the page in the magazine they physically came from (like 116-132) with pages they added labeled differently (like a page just called "Credits" at the end). I'm assuming we should ignore all that and go with a standard numbering order (even on scans that have page numbers on there) since this is simply to denote the numerical order of the pages in this file, correct? If so should it start at p000 or p001?
Also, if a manga title has a character that is simply unsupported in a windows file name (like a "?" or ":"), should it just be omitted, or should something else go there? Chrome will for instance when saving a web page replace unsupported characters like "?" with a "_"). I'm assuming it should just be omitted, making a title like "What:The" or "WhatThe?" become just "WhatThe", but figured I would ask.
Thanks!
Hey there! So, the naming scheme works really well... and it's great for sorting.
However, why do you separate group collaborations with a simple hyphen?
This makes it much more difficult when there's a group name that has a hyphen in it, and it also just doesn't look very good when it's all bunched-up like that.
Here's what I recommend for group collaborations:
[GroupA & GroupB & GroupC]
I doubt many groups use an ampersand in their group name, and, in fact, searching on MangaUpdates, I could only find a total of 8 groups with an ampersand in their name. (https://www.mangaupdates.com/groups.html?page=1&search=%26)
Compare that to the over 600 results I got when I searched for groups with a hyphen in their name. (https://www.mangaupdates.com/groups.html?page=1&search=-)
As long as there's a space before and after each ampersand, and as long as we still don't allow for spaces in the group names themselves, even the ones that do use an ampersand will still be able to be recognized as a single group.
For example:
Manga Name [lang] - c001 (v01) [Binggo&CorpTranslations & Fire&IceScans & Manga-Underground]
Another option is to use a plus sign, and the numbers are actually in favor of this, as can be seen by this search on MangaUpdates (https://www.mangaupdates.com/groups.html?page=1&search=%2B)
However, I just don't really like the way it looks.
For example:
Manga Name [lang] - c001 (v01) [NoseBleed++ + Daiz + Illuminati-Manga]
As you can see, it's possible for the plus to come at the end of a group's name, which just looks really messy in this case. This isn't true of ampersands, as there would always be something before & after an ampersand, so the issue can be avoided there.
Anyway, is there a serverside reason for not using one of these symbols? Are you just looking to avoid "%26" or "%2B" strings in your URLs? Or was it simply not considered until now?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.