Quote:
Originally Posted by Turtle91
Also, this js technique is not strictly necessary on a compliant device. Simply linking the ePub3 css file AFTER the ePub2 css file would work the same way. RbnJrg’s js technique protects against non-compliant devices/apps by only linking the ePub3 css if it can run js. Thus you wouldn’t have decrepit devices ignoring all the css if it didn’t like one.
|
Exactly! I developed this hack as a workaround for epub ereaders based on ADE 2.x (RMSDK).
Quote:
|
A compliant device would do this automatically by ignoring css it doesn’t support.
|
That's right.
Quote:
|
This js technique can be used in multiple ways, however, and is a great step in learning “fall-back” coding theories.
|
With this technique is easy to convert an epub2 into an epub3. It's not necessary to erase nothing; just to add a new css stylesheet with the new properties for existing styles. And one doesn't have to worry about compatibility with old epub ereaders because the new styles, they only will be loaded (and will overwrite the existing ones) by epub3 ereaders. The issues with ADE 2.x are gone!
You are welcome
