Content Kindle Comic Converter - Convert comics/manga to MOBI/EPUB

[badbob001]

I'm currently trying to get rid of page numbers from a book and the page number text is the opposite color of the margins (eg: black text over white; white text over black). The GUI version works most of the time, but I want to see if it can be improved.

In the CLI version, I see --nocutpagenumbers, which is to disable the cutting of page numbers, but I don't see settings to tweak the page number removal process. What exactly is happening when it tries?

One idea is to determine the margin color, fill in the margin with the opposite color, determine the margin trim area based on the new margin color, and then apply that new trim area to the original image. The idea is to fill the margin with a similar color to the page number text, which will make it easier for the margin trimming to ignore the page number text. There is a danger for the fill to enter the content area if the layout doesn't use panels, but a workaround is to limit the margin filling to a specified area, like x pixels from the bottom.

[AcidWeb]

Options to set trimming threshold are not yet merged in main branch - they are available only in dev branch.

Both trimming attempts examine variance of the image bands and continue cutting until variance reach the threshold. Simple but effective method implemented by Mangle author.

https://github.com/ciromattia/kcc/bl.../image.py#L319
https://github.com/ciromattia/kcc/bl.../image.py#L372

[badbob001]

Testing the dev branch version...

For --croppingpower and --croppingpowerpage, what do the input numbers mean? Are they percentages from 0.0 to 100.0? So lower = less cropping; higher = more cropping?

When cropping margins/page numbers, it looks like it will stop cropping once the image dimensions is within the device dimensions. This can result in margins/page numbers remaining in the page, despite crazy high croppingpower/page settings. I thought if I use the -upscale option, it would continue to crop all the margins/numbers and then upscale the image, but it doesn't. Anyway I can override this?

Also, what does High Quality Panel View do? I thought Panel View just tells the device where the Panels are and not related to the image size but the resulting file is almost double in size.

[badbob001]

Actually, I may be wrong about why the cropping stops. Using customwidth and customheight, I set the dimensions to being much bigger than the image and also much smaller than the source image. In both conditions, the same pages show the same cropping results, so I have no idea why the cropping stops sometimes.

See attached images (resized to fit forum limits):
1,4: Some margin left from the top of the page
2: Part of the page number is left on the botton
3: The whole page number is still on the bottom

I'll investigate to find a lossless jpeg cropper and just uniformly crop out the bottom x number of pixels from all pages to remove the page numbers. This way, KCC just has to worry about finding the margins.

[AcidWeb]

Sky is the limit. Higher = more cropping.

Cropping definitely don't stop once the image dimensions is within the device dimensions. Processed image can be smaller than device resolution.

https://github.com/ciromattia/kcc/wiki/HQ-mode

Additionally remeber to use EPUB output to test it. Images in CBZ will be always resized to target resolution. In most cases that will add margins.

[hhtien1408]

@AcidWeb: How to force KCC convert Manga into AZW3 instead of MOBI? How to strip out source from MOBI to decrease converted size? I'm using KCC 5.0.1

[AcidWeb]

Ouput is hybrid MOBI/AZW3 file. Source is already stripped.

[hhtien1408]

Hybrid? Hope you can explain more in detail.

How to edit metadata (author, title) for the converted mobi? I've already edit Calibre but it made no sense when transferring into my Kindle. Mobiperl did no work, Mobi Header Editor also. Hope you could help me! Thanks

[AcidWeb]

It is simply MOBI file that is old MOBI and AZW3 file at once. That is default and only file type created by KindleGen.

Calibre don't support editing metadata in this type of files.

Easiest way is setting metadata before KCC conversion. If you really want to use Calibre for that you need to create pure AZW3 file with KindleUnpack plugin.

[hhtien1408]

How to edit the metadata before converting? Please help me with detailed instruction.

But this method damages the Panel View or not? HQ Zoom is checked.

Thanks a lot!

[AcidWeb]

https://github.com/ciromattia/kcc/wi...cRack-metadata

[hhtien1408]

But my source is jpeg (Dragon Ball - Vol 1 in Vietnamese translation). What should we start with KCC and ComicRack?

Convert it into CBZ, then edit with ComicRack and then?

I would like to get Mobi or awz3 with edited metadata to read on Kindle Paperwhite 2. Not CBZ

[AcidWeb]

No... Pack your files. Change extensions and use KCC metadata editor.

[hhtien1408]

How to pack files? Which files? Help me!

About Kindle Unpack, I have splitted hybrid Mobi/KF8 into AWZ3 to edit with Calibre. It worked in changing metadata! Thanks!

[AcidWeb]

CBZ = ZIP. CBR = RAR. CB7 = 7ZIP.

Just pack your source files.