I'm putting together LRF formatted tune books for traditional Irish music, have had very good results generating the PDF books from my scoring application, then converting using RasterFarian.

Ideally, I'd like to have a table of contents entry per tune, but that can get unwieldy to navigate, some of my books have over 1000 tunes, which would be over 100 TOC pages. I've fallen back to just having one TOC entry for each starting letter, but even with that, its not very useable since there can be 50 or more tunes in each letter.

The problem is that I can't see a way to quickly jump through long sets TOC pages (like is available for jumping 10 pages forward in the book) to get to the TOC page of interest.

An alternative would be to have some sort of hierarchical TOC organization, but as far as I can tell, the device flattens out any sort of hierarchy in the PDF TOC. Am I missing something?

I've searched the docs and this site, haven't found any tricks or shortcuts. Is this possible on the device?

No way to do it with the Reader's own TOC, but if you're using software which lets you generate "links" within a document, you could always create your own hierarchical TOC using hyperlinks. I've done something similar with the various "anthologies" I've posted to the "Book Uploads" forum section - I start each one with an index of books, and then each entry in that takes you to a separate "Contents" page for that book.

I guess that perhaps RasterFarian perhaps flattens the TOC structure when converting the PDF docs. I can't use the PDF versions of the files, the reader really seems to choke on 1000+ PDF docs that are all images, so conversion to native format while retaining the TOC hierarchy would be the ideal and desired solution.

Since with Hyperlinks TOC matter would not have to go at the beginning of the book, how about starting out with a simple A B C D E F G kind of toc all on one/two lines.

A Link for Styles
A Link for Songwriters
A Link for Sets

Each of these links would jump to full links at the END of all the documents...

It would have one section for the Alpha listing - all for A - all for B - all for C
Then it could have a second selection, by Style Type - then alpha within that...
It could have a third section by Songwriter - Then alpha within that
It could even have a section by your favorite sets...

All of this at the end of the document where you wouldn't ever have to scroll through it...

I wonder if something like this would work....

How does BD handle one to many links... it seems to be capable of doing it...

I just finished support for an HTML -> LRF convertor that converts <a> elements to buttons in a LRF. It can process HTML files recursively, thus theoretically it should be able to handle any depth of TOC though i've only tested it with 3 levels.

I just finished support for an HTML -> LRF convertor that converts <a> elements to buttons in a LRF. It can process HTML files recursively, thus theoretically it should be able to handle any depth of TOC though i've only tested it with 3 levels.

Its still in svn so if you're interested I'll expedite releasing it

If it works on Windows, I'd be interested in giving it a try. Does it handle external fonts? And graphics such as drop text?

It puts graphics on separate pages. At the moment it doesn't handle external fonts. It does handle font-families, substituting the equivalent reader font for them. And yes it work on windows. It will be in libprs500-0.3.13.exe which I will release sometime this weekend. Get it from https://libprs500.kovidgoyal.net

It's still very much alpha quality, so you may have problems, but I'll help you fix them.