Quote:
Originally Posted by RbnJrg
Yes, but if are going to write the heigh and width with the property "calc" (dangerous under epub2) is better your first aproximation with <img with="xxx" height="xxx" ... />. The ereader will make the calculations and it will work everywhere. But again, the issue to write for each image its size  I still continue thinking that your best bet is to build two epubs. For Kobo you only need to set a measure (i.e. width: 30% or whatever) and just with a class. And for Google Books, to include the images with my second way of doing it. And so also to employ only one measure, the width, and also with a class. |
But then how to distribute two different files?? I check on the platform that 99% of our clients use, and you can specify different files according to the reseller, like a file for Apple, a file for Barns & Nobles, a file for Kobo, a file for online libraries, but then it’s still up to the reader to choose whatever apps he wants to view the ePub. So I really don’t see how we could make a file specifically for Google Books.