Thread: Preventing Sigil embedded font files from user access
View Single Post
Old 02-15-2015, 07:49 PM   #13
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,109
Karma: 148951733
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Hitch View Post
Bob:

Things have changed QUITE a lot in the last 3-4 years. I strongly recommend that you simply subset the font, using either Toxaris' program or the Calibre font subset in...POLISH ePUB, IIRC. The obfuscation method is likely what CAUSED your problem. Font Creator is not the same as these other methodologies, which are simple subtraction.

Hitch
So if Charis SIL is subsetted and the name changed internally and externally, will Amazon no longer recognize it as Charis SIL and not remove it?
JSWolf is online now   Reply With Quote