Originally Posted by DaleDe
Typically supplying a default override CSS will allow even someone who is not to good at writing CSS to make a few changes to an existing file.
The way our app works, we don't really have the ability to "strip" CSS, we can over-ride specific "known" tags. So we could hypothetically make a "default" over-ride sheet (and probably not that hard to make the "visible" in the file structure for power users to edit), but when the book used non-standard "named" selectors, or inline CSS it would still apply. Our default over-ride would be used when the user turns the "Use Publisher's Formatting" is turned off. And then the interface would essentially "edit" that over-ride CSS. Note that a more accurate label for that toggle switch would be "override publishers Formatting" - where "on" would be the equivalent of the current "off". That string does not fit though...