04-24-2012, 06:11 AM | #346 | ||
reader
Posts: 6,975
Karma: 5183568
Join Date: Mar 2006
Location: Mississippi, USA
Device: Kindle 3, Kobo Glo HD
|
Quote:
Quote:
|
||
04-24-2012, 07:54 AM | #347 |
Evangelist
Posts: 456
Karma: 1044878
Join Date: Apr 2009
Device: Kindle Paperwhite 4
|
Yes, but they also set linear="no". Which means that ADE will see it & pull a cover from it, but you won't actually see it when you open the book - which wouldn't address jhowell's complaint.
|
04-24-2012, 08:33 AM | #348 |
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Which means that ADE could do it (not show it when you open the book), but as far as I know, ADE just ignores linear="no", i.e., it displays it as anything else.
|
04-24-2012, 09:05 AM | #349 |
Grand Sorcerer
Posts: 27,550
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
To be fair, I think if Mobi_Unpack were to generate an initial (manifested) XHTML page with the cover image in it, it would be making assumptions about the original source that it couldn't possibly know. The only thing certain that can be ascertained from reading ePub specs is that there is no official way to handle cover images/pages in an ePub. So the bare minimum of properly manifesting the image and adding the <meta name="cover" content="blah"/> tag seems appropriate to me, in this light.
|
04-24-2012, 01:43 PM | #350 |
Grand Sorcerer
Posts: 6,497
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
I agree that it would not be appropriate for an unpack tool to generate new xhtml for the cover and handling it via metadata is the most sensible thing to do. That said, the full-size cover images in the KF8 files I have unpacked to EPUB are manifested, but not explicitly indicated as being a cover in the OPF. I suggest adding a name=”cover” meta tag (as per Amazon) and/or cover-image property (as per EPUB-3).
ETA: Ooops, my bad.. The cover meta tag IS present in the unpacked files. Never mind. Last edited by jhowell; 04-24-2012 at 01:50 PM. Reason: Correction |
04-25-2012, 10:39 PM | #351 |
Junior Member
Posts: 8
Karma: 10
Join Date: Apr 2012
Device: Kindle
|
Great job, Kevin. It's just getting better and better. I have previously generated a mobi file with embedded fonts using kindlegen 2.4. Now there seems a problem after unpacking and splitting into a mobi7 and a azw3 (KF8) file. The azw3 file can be opened by Kindle Touch but there's no embedded fonts any more. It might due to the lack of declaration of the fonts information in the manifest section of opf, I guess.
Last edited by xxy; 04-25-2012 at 10:43 PM. |
04-26-2012, 12:14 AM | #352 | |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Hi,
Simply run Mobi_Unpack on the split .azw3 file and examine the Log to see if the fonts were properly included or not. Perhaps the fonts were encrypted? Either way, unpack it and look to see what is up. If there is a bug, let me know here. ps. I can not recreate this issue ... I have tried it with various kindlgen generated sample files that have fonts and all of the fonts were properly included in the split version of the file. So I need more here if you wan to get this bug fixed. Quote:
Last edited by KevinH; 04-26-2012 at 04:02 PM. Reason: added request for more info here |
|
04-26-2012, 03:59 PM | #353 |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Mobi_Unpack_v050 is out
Hi All,
Here is Mobi_Unpack_v050 which is a pure bug fix release. Both bugs were detected and fixed by Kovid (Thank you Kovid) - fixed bug with unreliable decoding of zlib header by letting zlib handle it - fixed bug with images stored in urls in the style= attributes in tags in the main xhtml files Please post any bug reports here. Hope this helps, KevinH |
04-26-2012, 07:01 PM | #354 | |
Junior Member
Posts: 8
Karma: 10
Join Date: Apr 2012
Device: Kindle
|
Quote:
Curiously enough, if you check one step back, the .opf in the mobi8 folder is perfectly right (with fonts references and everything) when unpacking and splitting the original mobi. So I think this is a fixable bug. To make your debug easier, I will upload a test mobi file later on. Thanks again. |
|
04-26-2012, 07:55 PM | #355 |
Grand Sorcerer
Posts: 27,550
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I've created several combination MOBI/KF8 ebooks containing embedded fonts using kindlegen, and the azw3 file produced with Mobi_Unpack's splitter utility always performs exactly as expected. The embedded fonts work fine in the .azw3 files (just as they did in their respective combo file). Unpacking those .azw3 files results in ePubs in which the fonts are properly manifested in the OPF, and the embedded fonts are displayed properly when using ADE.
If you do upload a test file, be sure to upload a kindlegen-produced, combination MOBI in which embedded fonts are working the way they should (in the KF8 portion) before splitting. Last edited by DiapDealer; 04-26-2012 at 08:02 PM. |
04-26-2012, 08:19 PM | #356 |
Junior Member
Posts: 8
Karma: 10
Join Date: Apr 2012
Device: Kindle
|
Attached are the original .mobi file and the split .azw3 file.
mobi8-content_nodrm.azw3.zip Please also check the 2 pictures captured from my Kindle Touch screen and you will know what the problem is. Last edited by xxy; 04-27-2012 at 12:15 AM. Reason: remove the unnecessary attachment |
04-26-2012, 08:51 PM | #357 |
Grand Sorcerer
Posts: 27,550
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I couldn't say what might be going on with your Touch, but I assure you that the AZW3 file you uploaded has working embedded fonts and unpacking that same AZW3 file shows that the font-files are indeed properly manifested in the OPF file. The embedded fonts work as they should in the KindlePreviewer (and the Kindle for PC app), but perhaps there is something different about the Touch.
See if giving the file an AZW or MOBI extension (instead of AZW3) makes any difference. |
04-27-2012, 12:12 AM | #358 |
Junior Member
Posts: 8
Karma: 10
Join Date: Apr 2012
Device: Kindle
|
Thanks. I have re-checked the .opf unpacked from .azw3 and the fonts information ARE there. My bad, sorry about that. Looks like it's a Kindle Touch rendering problem now. Let's wait for Amazon's next firmware update then.
|
04-27-2012, 09:15 AM | #359 |
Grand Sorcerer
Posts: 6,497
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
I’m not sure what tool produced or manipulated it, but I recently came across a mobi7 file that contains several FONT sections with no data in them. This book is viewable in Calibre and Amazon applications, but caused mobi-unpack to fail. I mention this as a “heads up” in case others come across this sort of malformed file.
FYI: The error occurs in the struct.unpack_from call following elif type == "FONT" in mobi_unpack.py. I patched my copy to skip it if the data length is too short. |
04-29-2012, 12:04 AM | #360 |
Junior Member
Posts: 8
Karma: 10
Join Date: Apr 2012
Device: Kindle
|
Looks like it's not only a problem with the sideloaded "homemade" KF8 files, but also the purchased "legal" ones (https://www.mobileread.com/forums/sho...d.php?t=175999) on the Kindle Touch. Amazon really needs to address this issue sooner.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can i rotate text and insert images in Mobi and EPUB? | JanGLi | Kindle Formats | 5 | 02-02-2013 04:16 PM |
PDF to Mobi with text and images | pocketsprocket | Kindle Formats | 7 | 05-21-2012 07:06 AM |
Mobi files - images | DWC | Introduce Yourself | 5 | 07-06-2011 01:43 AM |
pdf to mobi... creating images rather than text | Dumhed | Calibre | 5 | 11-06-2010 12:08 PM |
Transfer of images on text files | anirudh215 | 2 | 06-22-2009 09:28 AM |