As most PG ebooks already contain a TOC inside the HTML, its pointless to generate another one.
Sigh, you are going around in circles. The issue is that you are generating MOBI files that do not correctly implement the TOC standard of MOBI files. The result of this is that when a user of a PG file clicks on the dedicated "TOC" button on their e-reader device, the MOBI file you generate fails to take them to the TOC. This is a file format failure on the part of the file format YOU are generating. Yes, the HTML files that the creator of the PG book often also contain a "TOC" in HTML format. IF, for example, you were to generate a toc.htm pointing to the "TOC" already in one of the books' HTML files and correctly link that toc.htm to your opf file, THEN when the PG user clicks on the dedicated "TOC" button in their ebook reader then that TOC button WOULD correctly function and it would take them to the TOC the user has already generated in one of their html files. Or alternatively, if they have already created a file called toc.htm you could just link to that correctly as required in the opf file and everything would work. Or, if you are generating a TOC in NCX format you could with trivial changes also generate a toc.htm which you could correctly link into the opf file and then the TOC button would also work. Or you could use Calibre ebook-convert software which would do this automatically for you and again everything would actually work. But, instead you continue to pimp the resulting MOBI file format because YOU think YOU should be the one to choose which devices PG users should be reading on, rather than generating valid files in the file formats that PG customers need to read on the devices they already own. I think this is silly. Let the marketplace decide. If Amazon acts in an onerous way to customers then customers will choose to buy from Apple and read in EPUB format. If Apple acts in an onerous way to customers then customers will choose to buy from Amazon and will read in MOBI format. Having the choice helps drive the e-book vendors into less onerous behavior -- hopefully! -- So far all that Apple has succeeded in doing is driving up the price for new releases for all ebook readers from $9.99 to $15.99 -- thanks Jobs, that's quite an accomplishment! -----Original Message----- From: gutvol-d-bounces@lists.pglaf.org [mailto:gutvol-d-bounces@lists.pglaf.org] On Behalf Of Marcello Perathoner Sent: Monday, February 01, 2010 11:57 AM To: Project Gutenberg Volunteer Discussion Subject: [gutvol-d] Re: Formats and gripes James Adcock wrote:
2. So all Kindle books should have both logical and HTML TOCs. Users expect to see an HTML TOC when paging through a book from the beginning, while the logical table of contents is an additional way for users to navigate books.
As most PG ebooks already contain a TOC inside the HTML, its pointless to generate another one. -- Marcello Perathoner webmaster@gutenberg.org _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d