Quote:
Originally Posted by KevinH
1. Perhaps I broke something in the last update? I will look into that. Forcing it to overwrite titles can be made an option for the future but wouldn't it be easier to use Find and Replace to empty all titles if that is what you want before running the plugin?
|
Yes, that could be done easily enough. But since the plugin is going to run anyway, it would be even easier.
Quote:
Originally Posted by KevinH
2. In the xml header? Hmm I have not noticed that but trimming can be added to remove any duplicate space. I will look into how it is being serialized.
|
Yes, in the xml header. The spaces are adding up for every run (I ran it multiple times just for testing).
Quote:
Originally Posted by KevinH
3. Yes. Unlike Calibre which ignores that part of the spec, a doctype is required. Especially for epub2 as the doctype is what specifies that named entities are allowed and which ones. Calibre kind of punts on this by removing and all named entities so that it can live without a doctype. That does not meet the spec. Sigil fully supports both named entities so the doctype is not optional. epubcheck has an open issue to check and require this.
|
Ok, so it is required for epub2, but not for epub3, right? I've seen Matt Garrish stating that it was not necessary for epub3:
Quote:
|
EPUB 3 uses XHTML5 for content documents, so a doctype isn't required. Adding the HTML5 doctype isn't harmful, either.
|
Source
And just a suggestion: It would be nice to have summary of changes. There is no indication that the book was even modified, unless you look around.