Quote:
Originally Posted by jacktanner
If someone puts together a patched build that generates a collections.json file, I'll be happy to test with my Kindle and report back.
JSON is a pretty easy format to generate (and to validate), but I don't know what the fields are for collections.json . |
I did calibre's JSON metadata cache stored on readers and the collection work for Sonys. JSON is not the problem. The problem is determining for the Kindle what works and does not work, and what means what in the pseudo-DB. It took weeks to work out what the Sony's DB fields mean, and I am still discovering gotchas.
This thread shows one recent example.
I can't imagine attempting similar work for a Kindle without a Kindle in hand. The initial development and subsequent maintenance would be very painful, with no personal benefit.