Quote:
Originally Posted by JSWolf
You can't update RMSDK on a Kobo. People who view it on a Kobo with RMSDK could complain because it doesn't look correct. Then it will have to be fixed when enough people complain.
So how do you update software that you have no control over when the device is brand new or the firmware is brand new? You don't. You hope whoever designed the eBook knows what he/she is doing. And having to code so it works on an older RMSDK is something eBook designers have to deal with.
|
If you buy a pressure cooker which, due to a design flaw doesn't actually fully seal, resulting in a slightly lower cooking temperature despite it's nominally being "at pressure", is it reasonable to expect that all recipe writers should incorporate these kinds of idiosyncracies into cooktime guidelines?
Or is it more reasonable to expect the consumer to either a) complain to the manufacturer, or b) buy a new pressure cooker?
But beyond this little thought experiment, I think the more illuminating feature of this back and forth is that all of your contributions have been to say that everyone is doing it wrong; there hasn't been a single line of CSS that you have put forward as an alternative that would satisfy your criticisms while also addressing the topic at hand....
Of course, you don't owe anybody any solutions, particularly if you are a paid ebook creator who has a proprietary interest in maintaining a competitive edge. I couldn't really hold that against you. But then responding to help queries just to say that everyone's code is wrong without offering your own as an alternative seems like a bizarre way to participate in a help forum/thread. It makes more sense to just let everyone keep pumping out comparatively bad ebooks, while you reap the professional rewards for being the only that does it right... right?