View Single Post
Old 05-15-2018, 03:54 PM   #1166
AcidWeb
KCC Co-Author
AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.
 
AcidWeb's Avatar
 
Posts: 845
Karma: 765434
Join Date: Mar 2013
Location: Poland
Device: Kindle Oasis 2
Cropping is essential part of process. I'm fully aware it can be problematic in some edge cases but that will not change.

I'm aware that "bumper" pages are butchered. Entire algorithm is fine-tuned to optimize "normal" pages and "bumper" images are considered casualties of war. This tool was not created for publishing purposes to create perfectly formatted books. It was created to make "normal" pages as readable as possible.

Power users can experiment with CLI version. But lack of cropping can cause major problems with MOBI output (and even bigger ones with KFX output).

Please remember that KCC officially support only Kindle and Kobo devices. I'm always open to tweak something for other devices but I have to draw a line somewhere.

@ilovejedd - CLI version (and entire KCC) work correctly on 32bit machines. Lack of 32bit binaries is QA issue. Maintaining entire build pipeline require more work than application itself :|

Last edited by AcidWeb; 05-15-2018 at 04:18 PM.
AcidWeb is offline   Reply With Quote