Quote:
Originally Posted by JustinThought
As far as your second scenario, the same occurs with the stylesheet.css, and any external fonts. IMHO, this is more of a protection than a problem.
|
The use-case on #2 is: I have an old EPUB + I have a set of template files:
- cover.xhtml
- titlepage.xhtml
- stylesheet.css
- cover.jpg
- [...]
I plop template files into the EPUB.
Many times, the old EPUB has the same common filenames.
If there was a conflict, then you should be able to overwrite/skip (just like you currently can with images).
Currently, you have to remember which HTML files were conflicts, then manually delete them out of your book, then readd the template files all over again.
Most of the time, I only notice the title page wasn't overwritten until quality checking, and then it's just easier for me to copy/paste code instead of using the
Add Existing Files functionality.
This becomes quite the pain when the amount of replaced files becomes large.