Version 1.7 beta #282
Merged
Version 1.7 beta #282
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The goal is to use the content key (base64 encoded) as a parameter for lcpencrypt in order to manage content update (with the same content key) without re-creating a license for the user.
llemeurfr
changed the title
This issue is somewhat related to w3c/audiobooks#61. The Readium manifest converted from a W3C manifest references the W3C Primary Entry Page; it is therefore copied in the new package. No need for a specific treatment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
lcpencrypt: add the possibility to force a storage filename different from the unique identifier of the content
Also replaces every occurrence of .rpf (non-existent) by .webpub (official extension).
Plus minor cleaning of the codebase.