Quote:
Originally Posted by davidfor
Yes, I think so. Being able to use a URL for the included stylesheet would solve my "use site stylesheet" suggestion. And if the adapter creators find a suitable URL for the stylesheet, then this can be included in configuration files but commented out so users can use it if they want to.
|
That seems fair. Another possible option would be adapter creators putting FFF-specific-site-specific CSS files in github or somewhere and linking to those.
Quote:
Originally Posted by davidfor
You probably don't want to open this..
|
Listing more than one file/URL in INI is a possibility--and I'd much rather have the suggest before I add code rather than after.
But if I do that, they'll just get concatenated together into one CSS file in the epub; which should be functionally equivalent. And for html output, the CSS gets embedded.
There are some complex interactions I want to consider first about precedence and ordering for files, CSS in the INI, and [sections] order.
I'm also considering the possibility of making it a general feature (like
add_to_), applicable to other (all?) settings.
replace_metadata comes to mind.