View Single Post
Old 07-13-2021, 01:13 PM   #5
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,828
Karma: 6120478
Join Date: Nov 2009
Device: many
When you import or load an epub into Sigil it will automatically grok utf-16 (and many other encodings) and convert it to utf-8 which is now an industry standard. The problem with any other utf- encoding is that they are endian dependent (little vs big endian). So you would need to specify either utf-16 little or utf-16 big and then use the appropriate Byte Order Mark (to indicate endianness).

There is no such thing as characters above the utf-8 code point encodings. Utf-8 can represent the full range unicode codepoints.
KevinH is offline   Reply With Quote