Originally Posted by NogDog
Is that because of the hash-like names used for them in the collections.json file? (I was looking at it awhile ago and gave up trying to figure out what hashing/encrypting algorithm they're using to come up with them.
I've already worked out how the hash-like identifiers are encoded for both DRM and non-DRM files, so there's no problem there.
The code I'm testing right now (v0.4) uses (and creates) these identifiers and now supports PDF, MOBI, PRC and AZW files. I'm currently adding Topaz support.