Quote:
Originally Posted by spelunker
Pointing out the obvious:
ALL of this could be avoided by generating your toc through the head element <title> as I suggested.
Real books have some pages without big honking titles. I would like to emulate real books. Why do you want to force me to do anything different? Now you're all talking about how to get around the requirement, oh, but kindle doesn't like it so you can't do it with kindle books. What if you change the requirement that shouldn't be there in the first place?
Are you interested in making the app better? This would make the app better.
|
You are kidding? I have many books from various BPH (with 1000 line CSS) and many do not even use what we have (correctly?).
<rant> 10+ years of EPUB and they still keep trying to make it LOOK like the paper edition, forgetting that there is no Size slider on that dead tree, No fold out for wide images and a dozen other
tricks Printers have been doing.
Paper = the way Publishers want it.
E-book = the way USERS want (OK, Try to have) it. And my latest gripe: Designing (simple novels) for i-pad sized screens (resolution and size. we really need 1200px fleurons?)
</rant>
Nil Title tags, (not that my devices even use those that are set).
Cr*p Alt= ('image 42', gimme a break, what does that really DESCRIBE to a person with poor vision).
Inconsistent use of styling from chapter to chapter (there is a reason for those BPH 'house' STYLE SHEETS. but it does no good if the person coding ignores the classes defined)