Quote:
Originally Posted by Ertagon
Kindle Comic Margins
What current CBZ -> AZW3 in calibre looks like [ link]
What it looks like from Kindle Comic Converter [ link]
Justification:
Kindle Comic Converter (KCC) - is generally slow, supports few formats and does not integrate well into the Calibre ecosystem. It's generally painful to use at scale.
Todo:
- Modify the CBZ input to have a "Kindle margins remove" or create a separate input just for this. It should maintain all of the CBZ input functionality. Any other implementations are good as long as they make sense and allow for/include the original CBZ functionality.
- Investigating the KCC python code and the output itself might prove insightful. Example of .epub output from KCC [ xhtml], css, content.opf
- Read Amazon's documentation
Goal:
A publically available plugin which essentially replaces KCC by implementing CBZ conversion that does not produce extra margins, as shown in the links above. The plugin should not have any breaking bugs. Maintenance is not expected.
Reward: €100 (payable no sooner than 9/01/2023) + €50 (if W/B margins functionality from KCC implemented).
Awarded upon successful completion of the plugin.
Award email: jaroslawjanas.dev@gmail.com (email me before publishing it)
To give this posting validity, here is my GitHub profile
Note: If this remains uncompleted for a more extended period of time, I will do it myself, but it might take a considerable amount of time since I am completely unfamiliar with the Calibre codebase. I'd instead give someone the money since it will cost me more (in time) to do it myself.
If the plugin/behaviour is added without claiming the reward, it will go towards funding the Calibre project.
Feel free to email me with questions. |
I took a look at the KCC (command line) code a few months ago, as it was the closest thing to my use case (make photo albums from a set of images, with landscape spreads that join smoothly when in 2 page mode on a tablet, and scaling up and down for 'best fit').
I had some success hacking to get it to do this, but reached a point where I was struggling too much with the way the code is structured, and concluded it would be better to start over from scratch.
The KCC IMO is not well structured, it seems to do too many things to do any of them well, and the greatest Python sin of all, it doesn't conform to Python naming conventions or PEP8 generally.
I think one of the KCC developers had a project to create a calibre plugin, but they wanted to use Python 3 features which wasn't supported at the time so it probably isn't much of a starting point.
So I would agree it's better to start over with a clear list of requirements, as I plan to do with my photo album idea, should I ever get around to it.
If you don't find a willing recruit, you could just build a command line tool, get that working, and worry about the plugin stuff later. Which is my plan.