kcc
kcc copied to clipboard
ciromattia
[Feature Request] Combine multiple CBZ files
Option for cbz files to be converted and compiled into one epub output.
At the moment I unpack cbz's, rename the folder to the chapter number, compress the file back to a zip, then append .cbz. KCC then converts the new file and all is good. Sometimes I will have to do this 100-200+ times for single chapters not placed into volumes yet.
I have tinkered around with EpubMerge in Calibre but the resulting image on my Kobo Sage is altered and gets clipped on the right side and bottom.
Greatly appreciate all your work, thank you.
You can skip the repack to cbz step, you can just use the volume folder you created directly. @User28237489
You will need to come up with a script (Bash / Batch file) and run it on PC.
KOReader is for reading, not creating/arranging books.
I do some stuff myself for CBZ manga on PC:
- KCC to prep double-side pages, upscale
- Unpack
- Apply dithering (because KOReader on Android doesn't support it).
- Then pack everything back with 7z to CBZ using a script.
Sorry guys, I completely confused the github project xD please ignore my comment above.
Why are you unpacking and renaming files in the first place?
Closing for now, re-open if you have more details. Consider an external cbz merging program like Comicrack.
Manga chapter CBZs are released as they are translated each week. My workflow is selecting all and unpacking which results in folders (chapters) of images. Sometimes these need to be renamed to not throw an error message in KCC. Selected chapter folders are dragged into a new single folder create a volume folder. New single volume folder is compressed into a single zip. Resulting file is run through KCC to build an epub.
Comicrack is Windows only. Only have seen manual solutions for Mac.
Would be cool if, for example, ten CBZ files are dropped in and with the option checked KCC could spit out one single epub.
New single volume folder is compressed into a single zip.
This part is not necessary, you can use the folder directly in kcc.
Your use case does make sense! Maybe a GUI option to autochunk by 10. I'll be honest and say that implementation probably will probably not be any time soon however. An external program might exist for Mac to do the batching. Or you could write a python script yourself.
Sometimes these need to be renamed to not throw an error message in KCC.
Which names cause error?
This part is not necessary, you can use the folder directly in kcc.
Oh cool, I'll try that out thanks.
Your use case does make sense! Maybe a GUI option to autochunk by 10.
Yeah! Combine into one file would be great. Perhaps the auto chunk could be a user set number.
Which names cause error?
kcc didn't like how one group named the pages for example:
[title] p001.jpg [title] p002.jpg [title] p003-004.jpg [title] p005.jpg
Where the third file was a two page landscape spread. Made a little automator workflow to rename everything straight through 1, 2, 3...
I'll be honest and say that implementation probably will probably not be any time soon however. An external program might exist for Mac to do the batching. Or you could write a python script yourself.
Yeah no worries. It would definitely be a great addition. I'm playing around with automator at the moment to get it to do this in the mean time. Thanks again!
kcc didn't like how one group named the pages for example:
[title] p001.jpg [title] p002.jpg [title] p003-004.jpg [title] p005.jpg
Where the third file was a two page landscape spread. Made a little automator workflow to rename everything straight through 1, 2, 3...
Which version of KCC are you using? The latest is v5.6.4 and there have been recent filename fixes. What is the error?
This ran for me fine:
@User28237489 We already have an EPUB-200 MB export profile that might be useful... Autosplit on 200 MB. Probably won't respect chapter folders though.
Checking back in, thank you for the help.
Which version of KCC are you using?
v5.6.4 was released the same time I started this thread so I was on v5.6.3. Issue has been cleared.
@User28237489 We already have an EPUB-200 MB export profile that might be useful... Autosplit on 200 MB. Probably won't respect chapter folders though.
I'm not concerned about the output size. Was this for legacy devices? Yes, I prefer to maintain the correct chapter/volume parsing.