Quote:
Originally Posted by JSWolf
Speaking of fonts, if you have an eBook where you need to embed font(s), then you should be able to have it as a KF8 only eBook since it won't work with Mobi. If you need features of KF8 that are not backwards compatible, then yes, a single format should be all that's for sale. The problem (as I see it) is because of Mobipocket, a lot of publishers are crippled and thus, they cannot make the eBook as good as it could be.
|
Forgive my moment of hubris, all, but: this is where you tell the wheat from the chaff. Or, to lapse into phrases from long ago and far away, the men from the boys. Where the cow eats the cabbage.
ANY competent (caveat word!) formatter can do wonders even with KF7, IF they know what they're doing. We use a variety of wee tricks, to ensure that the KF7 is nice, if not as awesome as the KF8. I personally put the books on my OWN K2, to test them, to ensure that they still look good.
If a book "needs" embedded fonts--like, say, for example, Kanji--then we bygod make them into images, and we embed them--inline. Yup. If the need is significantly greater--for example, I just had a book that had 8 different characters, all of whom needed (yes, you got it) their OWN font for their journal entries, I sit down and I discuss the KF7 challenges with the client, and how we can ensure that the reading public "gets" whatever it is that they are trying to convey, via the use of the myriad fonts. We'll make adjustmnents or suggest changes to the book itself (e.g., "Wolfie's Journal, Stardate X...") that can be hidden for KF8, and displayed in KF7.
THAT is
real "eBook" formatting. The challenge is, after all, conveying the content, the tone, and the meaning of the DT Book to the Digital sphere, and you can't just run something through Calibre and call it finished. /done being hubristic and braggy, now.
Quote:
|
Earlier today I finished reading Bucky F&%@ing Dent and in the eBook, the publisher put in some tables of baseball statistics/scores and they were put in as graphics. The problem was that the graphics were too small to be clearly read on a hi-res 6.8" screen. I could make out some just. If I had a 6" screen, none of it would have been readable. I used my iPhone's camera to zoom in so I could read easily. But, this could have been done as a table and it would have been readable.
|
THAT is simply stupidity. We embed our graphics at high-rez, and LARGE, so that they are VERY zoomable for reading. We learned that lesson a long time ago. What happened when you zoomed them, Wolfie? They were STILL too small?
Hitch