![]() ![]() They won't have chapters, but it will remember were you are. If we are talking about CBR or CBZ as the source, is there a reason you are not just putting these onto the device? Kobo ereader handle both formats and will allow zooming on the images in the comics. I can't tell you the differences as I don't really use either. I'm pretty sure that chapter for converted comic books are generated in different ways by KCC and calibre. And the formatting of the epub produced by both is different. A calibre conversion might downsize an image according to the profile, but it will not upsize an image. Are you saying that converting a comic to epub using calibre gives a different result than Kindle Comic Converter? Or are you converting something the KCC produced? Or something else?įrom memory KCC resizes images to match the screen size of the device you said you were using. To me those options will work best on my different readers.Thank you, but the image in the epub file don't fill the screen while it did when using kindle comic converter, i'm reconverting it because it shows only 6 chapters. Personally, for the cover options on the "KEPUB Output" page, I make sure the "No SVG cover" is unselected and select the "Preserve cover aspect ratio". That sets the defaults for new conversions.Īs you are doing a conversion, the page should be setup correctly for the image size. Reliable Kepubify can handle malformed books, and often produces better output for them than other software. You can change this each time you do a conversion, or via the preferences. Features Fast Kepubify is fast, supports batch-processing, and converts most books in a fraction of a secondaround 40-80x faster than Calibre. These are the only options that I can think of that affect the quality of the cover. That won't resize the images and will let the device handle them when you are reading. ![]() The output profile sets the maximum size for images in the converted book. What output profile do you have? This is on the "Page setup" page of the conversion. The only change it makes is to make sure the device can find the cover when it tries to generate the cover image.Įdit: This is where the output plugin stuff starts. The KoboTouchExtended driver doesn't actually touch the covers in the book. They give different results when you see the image. Epubs and kepubs use different renderers. Both of these can be fixed with the Polish books tool, the Modify ePub plugin, a conversion or using the editor.Īlso, it could be the renderer. This means that if you had a low resolution cover in the book, and found a high resolution cover, it might not have been updated or the display options won't be optimal. But, it needs to be able to find it, and it doesn't update the code that displays the cover. Calibre will update the cover image in the book when sending it to the device. If it is when reading, you need to check the actual code that is wrapping the image. Someone who cares about these images did some work last year to improve the quality. The driver generates the cover images directly from the covers in calibre and puts them on the device. If it is the latter, you might want to try the options to send the cover. Is there a way to modify the compression level?When do they look bad? In the book or when displayed as the cover image? cover pages) seem more compressed/distorted when using the plugin, expecially fonts that appear as graphics (e.g. Just one issue on kobo forma: graphics (e.g. ![]()
0 Comments
Leave a Reply. |