-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thorium Reader test results #53
Conversation
Wonderful! Thanks a lot @llemeurfr I have made a PR against this branch in #54 to add the LPF reporting. Otherwise, I checked out this branch on my own machine and, as far as I could see, the reporting with the ThoriumReader works fine. The report surely looks greater with that implementation added :-) |
Added the LPF reporting to the system
The codebase of Thorium Reader has evolved so that PEP and TOC are handled, and |
The resulting v1.5 will be deployed on early October. |
Thanks @llemeurfr, thorium is now part of the official report! |
This is the result of tests applied to Thorium Reader. It includes generic manifest processing, audiobook specific manifest processing, audiobook UA behaviors, LPF package processing.
The first shot applies to Thorium 1.3, release in June 2020.
In the coming days, other commits will be done, related to updates on W3C pub manifest handling (entry page, html TOC, case insensitive handling of rel values).