View Single Post
Old 03-01-2013, 09:25 AM   #141
ciromattia
KCC Co-author
ciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to allciromattia is a name known to all
 
ciromattia's Avatar
 
Posts: 88
Karma: 159872
Join Date: Nov 2012
Location: Rovigo, Italy
Device: Kindle 3 (Keyboard)
If I'm reading correctly, the page HTML should be constructed accordingly, e.g.
Code:
<div>
<img src="images/hij.jpg" alt="Comic Book Images" class="singlePage" />
</div>
<div id="pagehij-1">
<a class="app-amzn-magnify" data-app-amzn-magnify='{"targetId":"pagehij-1-
magTargetParent", "ordinal":1}'></a>
</div>
(from Amazon's Kindle Publishing Guidelines, pp. 38-39)

A bunch of comics are already on Kindle Store.

KCC uses Panel View to remove margins and - AFAIK - enable a sim-PanelView on Touch and Paperwhite - but as said I don't own a Paperwhite anymore, so I can't check.
I was wondering if Panel View's zooming is really a valuable feature, and in that case maybe cutting images and building a more complex and heavy .mobi (each image would be multiplied by 5 - at minimum) would be a nice enhancement, cause it would mean quite an hard work.
Also, I would need a Touch or a PW for testing

@AcidWeb: can't test the package right now, but if you built it with cx_Freeze it should be ok, can I add to the binary section on the README?
ciromattia is offline   Reply With Quote