Quote:
Originally Posted by DiapDealer
That crystalizes my understanding of the situ, believe it or not. 
Given that everything appears to be working as intended until some point in the KDP process ... that means there has to be something quantifiably different about the mobi built from a normal (valid) Sigil epub, and the mobi built from the "hinky," ePub-ish WinRar beast. It's possible that some of the raw, debug output of KindleUnpack might shed some light on what that difference might be. There's got to be something there (or not there) that KDP notices and says; "this we like," or "this we don't like." It's either that, or you've truly stumbled across a loophole that allows you to achieve something that they have no intention of supporting any more (embedded Type1 fonts).
Thanks for the GhandiSans pointer. I'll poke around and see if there's anything obvious to infer from any differences in the mobis built using the two different methods, but I'm certainly no authority. I just have a decent working knowledge of the "guts" of a kindlebook and of KindleUnpack's (formerly MobiUnpack) codebase. I'm a noodler. |
Well, I can definitively say that we have no intention of continuing in this vein--all these gyrations for a Type1 font. That's crazy. I'm only yanking my hair out because I have some books out there that I know I'll be getting calls about (fortunately, not tons); those few where we weren't able to discourage font embedding or able to switch someone over to a suitable font for chapter heads or what-have-you. And, let's face it--it's weird. And we all know how we MR'ers love us some WEIRD.
The other guy? Mathew? He has errata somewhere in his HTML. I was able to get his ePUB to build to a mobi with "sticky" fonts (ttfs) of the not-Type1 variety by nuking a bunch of his HTML chapters. I did make 1-2 small other changes, but it's obviously an open tag or...? somewhere in the body. I sent him the pared-down ePUB that does build, and the mobi I built with it, and told him "look between X and Y" for open tags or the like, and I suspect he'll be up and running shortly. If he just reassembles it one chapter at a time, he should be able to narrow it down adequately so that he can find the tricky beast, but his CSS, etc., was fine. His issue is separate and apart, albeit highly coincidental, to ours.
Hitch