View Single Post
Old 10-10-2019, 12:44 AM   #1285
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,053
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Rev. Bob View Post
Does the same thing happen under 1.3.13 or the semiofficial 1.3.14? I didn’t see anything in any of the merges I made for 1.4.0 that should affect fonts...
I removed and re-added the book and checked with the other two version of ModifyEpub I had around. It broke for all three. Easy solution was when I initially opened with Sigil was to select the font file and set Font Obfuscation to none. I vaguely remember that Adobe's font obfuscation uses the main uuid from the opf in the decryption so I'm wondering if the metadata update is breaking that.

hmmm... the original content.opf file contains these dc:identifier lines:

Code:
<dc:identifier id="uid">3500792716</dc:identifier>
<dc:identifier opf:scheme="UUID">urn:uuid:e6f8ccbf-f756-4a24-8f2e-7fa9b76df046</dc:identifier>
while the ModifyEpubbed content.opf file only contains the first of those lines:

Code:
<dc:identifier id="uid">3500792716</dc:identifier>
I've added an image of my ModifyEpub options for 1.40.
Attached Thumbnails
Click image for larger version

Name:	ModifyEpub_options.png
Views:	247
Size:	54.7 KB
ID:	174104  
DNSB is offline   Reply With Quote