View Single Post
Old 09-25-2013, 04:54 AM   #8
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by Tex2002ans View Post
What K7 fallback code would people in your company use in this situation?
The operating assumption here is that my company would find itself in this situation. We wouldn't. Not because we're rocket surgeons, to coin a phrase, but because we are very annoyingly diligent about explaining device/software limitations to clients. I would never (with all due respect to RbnJrg) invest all that time in putting images and captions in tables, for the very reasons I mentioned--on millions of devices, in the biggest marketplace for books in the world, that coding won't work or can create more problems. You'd have to come up with a contrived K7 "fallback" calling the image twice...nah, even that wouldn't work.

We tell our clients that if the captioning issue is that important to them, we can make the images with the captions attached, as images of text, or they can become accustomed to the idea that captions may very well break across a page/screen if someone enlarges their text. {shrug}. I spent a few years killing myself and my crews over this type of thing (like making outline-formatted TOC's work perfectly, when they are tabular in nature), and realized eventually that I was pushing a chain up a hill. It's a ridiculous thing to do. There are standards of care, and high-quality production, and then there's silliness caused simply because the very nature of ebooks is misunderstood (the ubiquitous square peg, round hole bit).

If a client is that obsessed with "images and captions must be" on the same page, then I tell them to consider fixed-format, which a) will give them exactly what they want; b) will require that we make a new book for each retailer, not format, c) cost a small fortune, due to all the minute, painstaking coding required for that, and d) severely limit the number of devices upon which the resulting tome can be sold. I have, curiously enough, found that when the price difference for a book goes up about $1,000, and the marketing and sales options decrease dramatically, most people decide that captions sticking absolutely next to their images just aren't as crucial as they thought they were.

Not to be derogatory about clients--not at all--but when it's your time and effort and brain-damage being expended, to make captions stick with images, a client will indeed stress over it, and send a book back to be revised umpteen times. If you charge for the actual costs of making a book that way (using either Ruben's table method, or the fixed-format), I generally find that things fall into perspective. Just my $.02.

Hitch
Hitch is offline   Reply With Quote