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.
|
Yes, and? All you have to do here is learn 5 minutes of CSS, spend another 5 learning how to add those via the NCX or the TOC-creation method, or either or both, and that's it. The only "forcing" being done here is if someone tries to use this as a WYWISYG ePUB generator, without learning how to write some nominal markup/CSS.
Quote:
|
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?
|
This has sweet nothing to do with "Kindle." It's about simply using the HTML and CSS to do what you wish. You can, in fact, do that with "Kindle" eBooks--anyone can. There are considerations, but it can be done. The sole consideration here is whether or not multi-level TOCs display on the Kindle for PC app, really.
For
THAT matter, you could write two different H1 heading styles. You could create one that's like the default--largish--and one that isn't--what you're requesting. This is basic HTML and CSS stuff and that would do what you're asking. Or, learn to add an h2 heading, styled as you wish--and include it in the TOC. That's almost automatic, too.
Quote:
|
Are you interested in making the app better? This would make the app better.
|
You mean, it would make it better for YOU, because you want it to be more push-button. It would not,
emphatically, make it better for me or, from what I see, about 98% of the other respondents here.
Hitch