View Single Post
Old 09-04-2020, 09:44 AM   #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,887
Karma: 6120478
Join Date: Nov 2009
Device: many
The first thing Sigil does when opening a file with obfuscated fonts is de-obfuscate the fonts so that Preview has a chance of actually working. So with broken fonts, Sigil could crash on startup.

A crash could be caused by anything the does not handle obfuscation/deobfuscation properly as fonts are binary data. The key depends on obfuscation version Adobe vs IDPF. In order to try to test things we need to know which obfuscation technique you are using (Adobe or IDPF, and both the opf bookid and any dc:identifiers that are type uuid in the opf, both before and after your changes.

This has nothing to do with font preview changes as once loaded in Sigil, all fonts are de-obfuscated.
KevinH is offline   Reply With Quote