Quote:
Originally Posted by Toxaris
IIRC the Adobe engine does not support the text-anchor in SVG at all. Other rendering engines might be fine.
|
Wow, this is all becoming sooooooo complicated, all just to do something that one would think would be so ridiculously simple, with the end result seeming to be "Oh, by the way, doing it this way won't always work." :/
Is this really all so necessary, going through all these complicated "jumping through hoops" just to do what it was that I wanted to do (and having it still
not work correctly in some contexts)? I mean, if it's not going to work 100% the time anyway, then with regard to what I came up with before, just using simple HTML (as I did up in the epub attachment that I included in my
earlier post here), I would think that with the size/orientation of the images that I was using that the only context in which the caption would bump over to the next page would be if one is viewing the book on a desktop/laptop computer, in a program where the windows can be resized -- and then the "problem" is easily fixable by resizing the window so that the caption doesn't bump over to the next page.
Isn't that better, to have a "problem" that occurs
sometimes but which the user can easily fix, rather than one that can't be fixed at all? Not to mention the former HTML method is so ridiculously simple and easy to do, and the latter is turning out to be soooooooooo incredibly complicated (comparatively).
Seriously, I'm just wondering what the point is choosing the extremely complex method, rather than the ridiculously simple method, when no matter which way you do it you're going to run into issues some of the time (and with the complex method the user can't fix it, but with the simple method they can).
