Quote:
Originally Posted by WillAdams
I'm going to go back and break apart all the diagrams and re-draw the images one part at a time, then will re-create things --- hopefully this will get the filesize down (they really shouldn't be that large, it's just the XML overhead of each path segment being its own object).
|
Sounds fantastic! From the SVG code, I see you use Inkscape, IF you want to generate the high resolution PNGs for EPUB/MOBI, follow my Steps 3+ in my "Formula to PNG Tutorial":
https://www.mobileread.com/forums/sho...d.php?t=223254
(Although you probably already knew almost all of those steps... and most of those beyond Inkscape steps can probably be automated using imagemagick).
Note: Try to avoid transparency in PNGs. While it would be fantastic to have transparency, I would avoid it at the current time, and just go with a white background. (See further down in that same topic where I ran into a few odd rendering bugs).
Quote:
Originally Posted by mrmikel
Be sure to try them in some real devices that need to display it when you get done. I think you are on the bleeding edge as far as real world devices goes.
|
Yes. DEFINITELY needs testing on a variety of different devices.
SVG is not really a well-researched topic in the realm of ebooks... I definitely haven't seen any advanced SVG like these interactive diagrams (just formulas, "SVG cover pages", SVG Title Pages, SVG captions, etc. etc.).
And I really have no idea how they transfer over to the old MOBI format. Last I knew, SVGs just go POOF... and the Amazon recommendation was "use media queries to swap a JPG or PNG instead" (although this would defeat almost the entire purpose of having the SVG in the first place).
Quote:
Originally Posted by WillAdams
They work on my old iPad, and in Chrome, and Firefox on PCs running Windows and Mac OS X and in Safari on Mac OS X --- I'd be curious how they work on Android tablets --- is there anything else I should test on?
|
Well as long as the renderer handles that subset of SVG, yours should run fine.... but EPUB3 explicitly bans SVG Animation, and so does MOBI/KF8 (as I linked above).
iBooks probably ignores that part of the EPUB3 spec (I don't know 100%, I don't have one to test on. It renders off of webkit, so if webkit can handle it, iBooks probably can), and AZARDI deliberately ignores that SVG animation ban.
Although EPUBs created with SVG animation ARE NOT EPUB3 COMPLIANT.... so if you "hack around" them to make them work, it won't be guaranteed to work on all the other EPUB3 devices/readers. And you most definitely will be causing yourself headaches in the future.
(Although we can also argue that ADE doesn't follow the EPUB2 spec exactly, and devices have all their own quirks as well... but that is a different topic!
)
Quote:
Originally Posted by mrmikel
Whatever you use or you think users of the book will use. If you've already covered that list, that's great. It is not likely to cover commercial ereading machines, but none of those is on your list.
A number of people on the forum are interested in a least having an option for commercial sales, that is why I brought the issue up. Kindle has the most users.
|
Indeed... for example, if you were designing an ebook specifically for iBooks, you would be able to get away with using some more advanced/complex CSS, using javascript, etc. etc.... but then you are severely limiting the reach of your market.
Quote:
Originally Posted by WillAdams
They work on my old iPad, and in Chrome, and Firefox on PCs running Windows and Mac OS X and in Safari on Mac OS X --- I'd be curious how they work on Android tablets --- is there anything else I should test on?
|
This should give you some idea on the SVG support (although we are talking BROWSERS, not ereaders):
https://en.wikipedia.org/wiki/Scalab...rowser_support