View Single Post
Old 01-09-2017, 12:05 PM   #4
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,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Is the encoding information (meta tag or encoding or codeset) properly detectable in the input html? In other words, how does a properly formatted ODF html file indicate the character set encoding it uses?

Once converted to utf-8, are these codeset or meta tags *removed* to prevent Sigil from being confused by loading a file that is actually in utf-8 but is tagged to be in some other codeset? Is the epub metadata properly setting the encoding to be utf-8 inside the epub it is handing to Sigil?

KevinH


Thanks,

KevinH
KevinH is offline   Reply With Quote