View Single Post
Old 04-06-2010, 05:38 AM   #13
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,015
Karma: 315160596
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by pdurrant View Post
I've just upgraded to 1.7.2 on Mac OS X. I'm still seeing my embedded encrypted fonts. (i.e. fonts encrypted with the script linked from this thread.)

If you upload a sample ePub that's failing for you, perhaps I can spot the difference that's causing the problem.
I have no experienced this problem. I no longer have an earlier version of ADE, so I'm guessing, but it seems that previous versions accepted opf:scheme="UUID" as identifying a valid uuid identifier, e.g.

<dc:identifier id="BookID" opf:scheme="UUID">c2ff824c-f984-4efc-844d-47875c302ba5</dc:identifier>

I'm certainly now seeing that the encryption key is only read if the urn:uuid: prefix is applied, and whether there's an opf:scheme="UUID" is unimportant.

So: make sure your have that urn:uuid: prefix on the identifier.

Last edited by pdurrant; 10-15-2013 at 09:16 AM.
pdurrant is offline   Reply With Quote