Quote:
Originally Posted by PoP
Just for information (at the occasion of playing with locking fonts of a book in this thread).
I noticed in the KindleUnpack of the sample AZW3, in the OPF <!-- BEGIN INFORMATION ONLY section, the entry <meta name="Unknown_(403)_(hex)" content="01" />
After removing this header, I found that the book opens with the ereader fonts instead of publisher fonts. I don't know which <meta name=?> triggers Kindlegen to generate the 403 header, but I thought KindleUnpack could possibly improve its decode from "Unknown_" to something like "Open With Publisher Fonts". |
I did some testing of the free sample of that book patched as you describe on my Kindle Oasis and have not been able to duplicate the results you describe. I am however seeing something very odd that works the same in both the patched and unpatched book.
I sideload the book and then immediately opened it and as you indicated the publisher fonts were not displayed. I then selected another font in the Aa menu and switched back to publisher font. After that the publisher font was displayed correctly.
In another test I sideload the book but then opened another book, closed it, and opened the sideloaded book. In that case the publisher fonts were displayed correctly from the start.
Finally I opened the sideloaded book and didn't see publisher fonts. Then closed it, opened another book, and went back to the sideloaded book. The publisher fonts were then shown.
So as far as I can tell there is a bug, but it does not seem to depend on the EXTH 403 field.