Quote:
Originally Posted by zoldier
This is not related jut to Kindle Previewer. I loaded calibre converted .mobi in two Kindle devices (old one and paperwhite bought last year) and both devices rendered it as I expected and how it looks like on Kindle previewer.
Based in this testing, my conclusións are:
1) Calibre converts from epub to .mobi in a different way that Kindle previewer does
2) Kindle previewer applies a 'wrong' convert policy because they think that their devices can not render something that they can or maybe Kindle previewer has a 'bug'
From my point of view, there is just one solution.
1) Decompile .mobi file converted with Calibre, because I know that it really Works on Kindle devices.
2) Get the HTML/css code from this 'decompile' file
3) Try to apply this code to my epub
4) Convert this new epub versión using Kindle previewer and load the result.
If this Works ... voilà, we have the solution
If not ... there are no solution because Kindle previewer is the "guilty" of this bad conversión and you do not have an alternative if you want to publish in Amazon.
What do you think? Could any one help me to 'decompile' this .mobi file? I saw a couple of tolos in this fórum to do it but they are implemented in Phyton and it is a 'new world' for me 
Thanks in advance! |
Question:
You loaded your test MOBIs at Amazon, and downloaded the Preview mobis, to ensure that the results are what you expect--is that right?
Because what you see, prior to uploading the file(s) to the KDP cannot be relied upon, for something like this, as an accurate view. The KF7 supports for the table elements were very, very poor.
And there are still millions of KF7 devices in the world.
Hitch