Quote:
Originally Posted by eggheadbooks1
The device in question is an older Sony Reader. And one cannot code for everything; it's become impossible. It's the nature of the technological beast: the speed of change and the vagaries of device programming mean that even what is considered "standard" code is not read equally across devices. In this case, the code works on everything we tested except someone with an old Sony Reader sees the text overlaying the image. There's nothing I can do about it: if I fix that problem for a minority user set, I create a new one for the majority of users. And once someone decides to go digital, they have to accept that, as with all things digital, obsolescence is their problem; they cannot get angry at content creators because the content doesn't display on an older device.
|
Hmm, I would definitely get angry in that case. If you are selling an ePUB2, than the ePUB2 reader should be able to read it. If it were an ePUB3, that is another case. If you deliberately create code that is not supported on older readers, you should either specify that or, and that is better, come up with a way where it fails gracefully.
My experience with a SVG containing a viewbox is that is only really works full screen as a separate HTML file. If I want to enter a real SVG file into the book itself, I just add it as an image and reference to it like an image (e.g. <img src="../Images/picture.svg" />).