View Single Post
Old 08-02-2016, 12:47 PM   #8
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,879
Karma: 6120478
Join Date: Nov 2009
Device: many
The unique id is used to encode/decode embedded fonts. Two different font encryption approaches exist (one Adobe's and one Idpf) and exactly how they encrypt/decrypt and exactly what part of the unique id string they use also seems to be not well specified so there are variations on that as well.

For Adobe's version I would remove the "urn:uuid:" prefix from the unique id in the content.opf and the toc.ncx (making sure they match) as I think only the uuid part is used. For idpf, they use whatever is provided in that unique id , leading to font encryption vs decryption issues depending on how these routines were implemented across devices.

Hope something here helps.

KevinH

Last edited by KevinH; 08-04-2016 at 09:41 AM.
KevinH is offline   Reply With Quote