Thread: Embedding fonts in AZW3/KF8
View Single Post
Old 07-12-2012, 07:12 AM   #23
pirl8
Pest
pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.pirl8 ought to be getting tired of karma fortunes by now.
 
Posts: 204
Karma: 239254
Join Date: Jan 2012
Location: Italy
Device: KT, PW3
Quote:
Originally Posted by KevinH View Post
Hi,

Kindlegen generated mobis have two headers and two EXTH sections, not just one. Have you tried setting the fontsignature payload to 0x2a in both mobi header exth regions to see if that impacts the problem? [...] Please let us know what you find out.
Ok. I did it.

I changed the fontsignature EXTH header via Hex editor in both locations as a sequence of '*'. Now calibre-debug -m my.azw3 reads:

Code:
fontsignature (300): '************************************************'
My Kindle Touch still recognizes embedded fonts and renders them well. Maybe the header has to be there but content is not important. Or maybe it has nothing to do with activating embedded fonts.

I will try to run Calibre from sources as Kovid suggested and add that header to see if the generated azw3 will behave differently.

I'm attaching my ePub sample if anyone else wishes to try.
Attached Files
File Type: epub p.epub (141.8 KB, 219 views)
Last edited by pirl8; 07-12-2012 at 07:33 AM.
pirl8 is offline   Reply With Quote