Quote:
Originally Posted by ksimpson1986
that being said, it has a massive table of contents with each day of the year being a link. This TOC is developed from indesign so it's already linked and ready.
|
I have worked on a handful of books that were massive TOCs with 500+ entries in them (compilations of newspaper articles over years).
Just organize and display the TOCs in a meaningful way, and the user can figure it out from there (skipping to a given year/month/day).
This is what sample code for an HTML TOC might be:
and use CSS to tweak the look:
I have attached a sample EPUB.
Side Note: If you are interested in both massive EPUBs, I wouldn't mind giving links if you wanted to see how those work on your devices. (One book is organized
Year - Volume.Issue - ~650 articles, and the other is
Year - ~970 articles.) I think the TOCs work perfectly.
Quote:
Originally Posted by ksimpson1986
the issue is, when viewing it in an eReader, the TOC is expanded by default, [...] i have created an extra entry of each month, and moved each of the 30/31 days of each month inside that monthly "folder". problem is, it's all still completely expanded by default.
|
I am not 100% clear on what is "expanded" and "folders", but I believe you are talking about the TOC.NCX?
Is this what you are talking about in the sidebar of Sigil?
Quote:
Originally Posted by ksimpson1986
when i view the TOC in the viewer, and tell it to collapse, it looks perfect. just 12 options, and you can expand each month to see each day. after i save it, it expands again automatically...
|
There is no way that you can control the display of the TOC.NCX on devices. It is up to each device on how they handle it (some might have the TOC fully collapsed by default, others might not).
If such a large TOC bothers you, maybe it might be best to just limit the TOC.NCX to Year/Month. (This can be done in Sigil using Tools - Table of Contents - Edit Table of Contents...).
Personally? I would just leave it how it is. Anyone who thinks the TOC.NCX is too cumbersome would be able to use the HTML TOC instead, where they might be able to navigate slightly easier depending on their device.