Quote:
Originally Posted by ThomasMcKean
But then couldn't yew leave out the font altogether in the CSS so the reader doesn't know the font is there? Then yew could override the font with the user settings.
Or is that just wishful thinking?
|
That should work the way that you suggest.
If you want to get into the software technicalities, my *guess* is that what happens is this. On application start up, the configuration is set up with the user interface settings, then if a CSS corresponding to the book format is found in /crengine whatever settings that duplicate user interface settings are overwritten by the settings in /crengine. Finally, any corresponding CSS settings in a book format that has CSS will overwrite once again. I did not get this from documentation, but simply from experimentation, so I may be wrong.
FWIW, I experimented with an EPUB that I configured for CoolReader to read instead of letting ADE read it. When I initially loaded the EPUB, it's CSS settings took over CoolReader's user interface settings and it was displayed according to the EPUB's CSS. Then I opened the EPUB on my PC and deleted it's CSS file. I reloaded the EPUB on the reader and again reopened it in CoolReader, and all my user interface settings were used for that EPUB. I am describing all this from memory of doing it yesterday, so I hope I described it correctly.
