Hello. Where do I make suggestions for future improvements?

[phillipgessert]

I think it’s just not the slam dunk improvement you think it is. Personally I’d find it a real downgrade, and all the advice in the thread is just folks telling you that what you’re looking for is already possible, and not real difficult.

[Doitsu]

Originally Posted by spelunker

ALL of this could be avoided by generating your toc through the head element <title> as I suggested.

Since the Calibre Editor already has that functionality, there's no point in adding it to Sigil, especially since it goes against best practices.

To generate a TOC from title tags in Calibre Editor:

1. Add the book to your Calibre library, right-click it and select Edit book.
2. Select Tools > Table of Contents > Edit Table of Contents.
3. Delete the default Start entry.
4. Click Generate ToC from Xpath.
5. Paste //h:title in the Level 1 ToC box and click OK.
6. Click OK again and select Save a copy from the File menu to save the updated epub.

[DNSB]

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.

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.

[Hitch]

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.

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.

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

[theducks]

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)