Quote:
Originally Posted by JSWolf
This is not attacking ePub 3. There's a reason not to use rem.
If you are creating an ePub for sale, it could get read on a Kobo as ePub and rem will not work. It could get read on a nook or an old Sony Reader where rem does not work.
So if you want to make sure you eBook does not break us em. ePub 3 should be made as backwards compatible as possible and rem is not going to help do that.
|
So, Jon, you really need to understand how css coding works. If a reader/device does not support a setting it is supposed to ignore it. So, you can easily set your css to take advantage of this…
Code:
p.largetext {
font-size:2em;
font-size:2rem
}
Will use rem because it is the ‘most recent style’. If the reader/device doesn’t support rem then it ignores it and reverts to the next ‘most recent style’ which is em.
The coder who builds the epub should code for epub 3.x/css3.x but provide fallback coding if their target market has some ancient relic devices still in their inventory.
These are VERY basic concepts.
There are more advanced techniques where you can even check if a property is supported (@supports) or if the device has specific properties (@media). Your assumption that an epub coder MUST only use ePub2/css2 to be backwards compatible is just plain incorrect.