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.
|
Have you looked at the <title> element in many real world epubs? I would just
love to to have a TOC where every chapter is the book title and author or the book title, those are fairly common practices for the title element. Then there are the books that have <title>Unknown</title>, etc.
Quote:
Originally Posted by spelunker
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.
|
Why do I want to emulate a paper book (what I assume you mean by your "real books" phrase)? A bit of an elitist attitude that ebooks are not "real books" seems to be showing.
I want my ebooks to be readable on my ereaders. I want to be able to change font size, line spacing, margins, etc. without making the rendered pages look like crap. If that means the layout is different from a paper book, so be it.