View Single Post
Old 01-12-2017, 10:28 AM   #14
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,805
Karma: 6000000
Join Date: Nov 2009
Device: many
Then the issue must be in the plugin someplace. Sigil autodetects the encoding and converts it to utf-8. The plugin should read the input file as binary (bytes), attempt to autodetect the encoding using charmap or byte search for an encoding string, and then decode the binary (bytes) into a python str type (unicode). Once as a python3 string replace any metadata encoding infonfrom the old encoding to utf-8 before using encode to create a utf-8 set of bytes for working with lxml and etc.

How does this plugin handle that process?

KevinH
KevinH is online now   Reply With Quote