Quote:
Originally Posted by JSWolf
One thing I do think needs fixing is to have the extra CSS added to the CSS and not to the HTML. I do not like messy code and having the extra CSS added to every HTML is messy code.
|
That was a trade-off I made:
Pros:
- Inline CSS is pretty much guaranteed to work.
- Can be done while transforming HTML.
- Doesn't need to modify the package document.
- No path resolving complexities.
- Won't further break broken books as much (kepubify aims to process broken books as best as possible and not make them worse).
- Not as bad as directly adding styles to elements.
Cons:
- Possibly ambiguous escaping of angle brackets.
- Duplicate CSS in each file.
- Not clean and harder to edit, but this doesn't matter too much (the book is generated and not really going to be edited directly after conversion).
If you have any additional disadvantages for embedded CSS, I'd be happy to consider them.