Quote:
Originally Posted by odedta
Hitch, why wouldn't a table solve this?
|
odedta:
If the poetry is short enough, you could get away with it, assuming that each stanza was in its own table, and each line in its own row. Remember that a) oldest Kindle devices don't recognize tables AT ALL, so you'll have a muddled mess with no fallback coding to save you; b) if a table is too long on most Nooks (too many rows), the device will simply flip PAST the entire table, as if it doesn't exist--you can't scroll through an overly-long table. The device flips to the next-screen-in-sequence, after the end of the table. c) Long tables in Kindle = no-no, because K2's and up to the mid K-3's (and, actually, not 100% sure about the new DX'es) will "lose" the table formatting if the table's rows carry over onto a new screen, as if the device loses its mind.
There's another reason I can't pull from inside the hollows of my brain, but those are the biggies. This is the ePUB forum, so really, we only care about b), here, but b) is a real doozy, and remember: you can't CONTROL the vertical size of the table, given that people can resize the font. If ancient Mrs. Jones sizes her fonts to uber-large, and the tables resize throughout, you could be in for a very nasty surprise. I remember the first time the "disappearing table" stunt happened to me...that was quite unpleasant, when I had a client who thought I'd omitted all their carefully-cultivated tabular data...but they'd resized it via font sizes, and the tables all disappeared, with the "page numbers" jumping a few digits at each "gap." Rude, that.
FWIW. As they say, your mileage may vary.
Hitch