[KevinH]

The bug is actually in ePub3-itizer and not Sigil.

Sigil actually has the tools to automatically change extensions. As this requires parsing the entire books for links and updating them as well if needed, this is something much easier done in Sigil than a plugin.

I will add some docs to the ePub3-itizer site that will point out that using .htm or .html when the text is actually xhtml is not a particularly good idea even at the epub2 level and that the user should fix this with Sigil's rename tools before invoking the plugin.

This distinction will be become quite important when epub3.1 (epub4) is finally approved as they must be able to distinguish between html code and xhtml code.

Thanks,

KevinH

Originally Posted by PKTC

To the makers of Sigil -- thanks very much! Your program has been most helpful. I's like to report a small bug. An html file converted to epub 2 by Sigil (Windows version) lists all sections of the book with the extension htm in accord with the extension on the html file. However, when that epub file is converted to epub 3 using the epub3 plugin, the .htm extension is not converted to xhtml as it should be. This leaves the mildly time-consuming task of manually renaming the extensions. Of course, if the original html file is given an xtml extension instead of htm, then there is no problem.

This is a small matter but one that would be helpful to be fixed.

By the way, I could not find the referenced help documentation despite searching for it. Basic procedural matter like the above should be mentioned in the documentation, if not already.

Thanks again.