Thread: sigil changes 'version' in content.opf from 2.0 to 1.0?
View Single Post
Old 02-21-2016, 06:50 PM   #6
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,816
Karma: 6000000
Join Date: Nov 2009
Device: many
Hi All,

This bug is now fixed in Sigil master. It will hit any OPF file that does not start with an xml declaration line:

Code:
<?xml version="1.0" encoding="utf-8" ?>
So the workaround is to edit the opf file and add an xml declaration to the first line of the file. Sigil does this automatically which is why we have not seen this bug reported before.

This bug fix will appear in the next release.

KevinH
KevinH is offline   Reply With Quote