Quote:
Originally Posted by JSWolf
You have to remember that Kobo are popular. And because of this, you really should be coding (when you can) so that your eBook works as best as it can with the version of RMSDK on a Kobo. There are things you won't be able to make work, but when you can, you should. For example, do not use rem but instead use em.
|
Are you saying that Kobo’s don’t work with blockquote and q??
If the OP is making a commercial product, then, of course, they would need to provide fallback coding for those ancient devices. As you also know, that should not prevent them from using current coding techniques to make their books look as good as possible.
The use of <article> and <section> are ePub3. The new standards should be used as much as possible if for no other reason than to keep them current longer. If those old devices can’t grok the new coding they are required to ignore them gracefully. That means they might have a slightly less-pretty product, but will be able to read it just fine. If the device doesn’t follow the spec, and crashes completely, then it’s time to toss the device… as you know.