Working with already-exploded EPUBs in v3 #725
-
|
It seems like the kotlin v3 toolkit no longer has built in support for treating an already-extracted zip directory as an EPUB asset. This was an option in v2 — you could pass a directory path to the streamer, and it would treat the directory like an unzipped archive. In Storyteller, I've been storing EPUBs on device extracted into directories. This is because:
What would be the best way to handle this? Should I write an |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
We changed this in v3 because we do not recommend using exploded archives for implementers. For your use case, you should be able to access the content of the audio files once the It is in fact still possible to open exploded EPUBs in v3, just not as obvious.
Instead, you can directly create a |
Beta Was this translation helpful? Give feedback.
We changed this in v3 because we do not recommend using exploded archives for implementers. For your use case, you should be able to access the content of the audio files once the
Publicationobject is opened by usingpublication.get()and theResourceAPI. However, I understand that this may not work if you depend on a third-party library for processing the audio files, which requires having the files on disk instead of accessing the bytes in memory.It is in fact still possible to open exploded EPUBs in v3, just not as obvious.
ArchiveOpenerwill not help you because it is meant to open a file (archive) as aContainerofResourceobjects instead of a singleResource.Instead, you can di…