In the manifest portion of the obvious epub, I agree, I don't see fonts showing up there. Indesign reported that "not all fonts could be embedded", which apparently botched several things in the output file.
In the manifest of the embedded test 2 epub, I am seeing fonts declared:
Quote:
|
<item href="OEBPS/Fonts/BemboStd.otf" id="added1" media-type="application/x-font-opentype"/>
|
And yeah, it dawned on me later that the reason I could see the fonts in sigil was that they were installed on my machine.
So the obvious example turned out to be not-so-obvious.
The Indesign-built epubs can be functional, but it's much harder than I want it to be. Hyperlinks are a bitch in indesign, and the obvious things you'd think would just work (like picture placements, text wraps, drop caps, multiple multi-layer tocs) either just plain don't, or don't work as expected. And there doesn't seem to be an indicator/guide that says what works and what doesn't.
I think that's all because of the approach adobe took into indesign: print first, epub should work like print, print forever, amen. Still causes me more problems than it solves.
And an epub is something between print and the web: it's a new thing!
-bjc