View Single Post
Old 01-29-2019, 06:00 AM   #11
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,801
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by momoha View Post
Well, there’s not only one case as I use SVG in all the books I produce (logos ans fleurons). I have been producing mostly ePub 2, but now I am analysing the possibility of switching to ePub 3 for all our books. Because of a lack of extensive testing of our files ( ), I haven’t noticed that Google Books problem before, but considering how much that app is used, it’s kind of a big problem for me, both for ePub 2 and ePub 3!

Thanks for your help, it’s greatly appreciated! Can’t get my head around this problem even after so many hours of research... kind of getting crazy with this.
Try in Google Books this new epub (epub2) I attach and tell me how it looks (I don't set the width or height in in the <img> tag, only in the css file). I'm using this time two different ways to include a svg (maybe one works better than the other).
Attached Files
File Type: epub SVG Image Size.epub (4.7 KB, 129 views)

Last edited by RbnJrg; 01-29-2019 at 06:03 AM.
RbnJrg is offline   Reply With Quote