Streamer "asset" URL, path relative to OPF (manifest items), failure with '../' step about architecture HOT 2 CLOSED

Well, I can imagine more edge cases.

Let's imagine the following EPUB:

META-INF/encryption.xml
cover.jpg
EPUB/package.opf
EPUB/chapter1.html
EPUB/chapter1.mp3
EPUB/navdoc/toc.html
EPUB/smil/chapter1.smil

Your suggestion should handle two problematic situations:

• accessing META-INF/encryption.xml
• accessing cover.jpg

For EPUB/navdoc/toc.html and EPUB/smil/chapter1.smil do you calculate everything based on the relative path of the Navigation Document, NCX and SMIL?

The Navigation Document would reference ../chapter1.html but with your suggested change, we would have to indicate EPUB/chapter1.html in the manifest.
Same idea for NCX and SMIL.

I can't remember if in EPUB content documents, links can start with a / with for example:

<a href="/EPUB/chapter1.html" />

That specific case would be very problematic because the navigator would attempt to access https://r2.org/EPUB/chapter1.html instead of https://r2.org/moby-dick.epub/EPUB/chapter1.html.

from architecture.

I think we should close this issue, as this is the active one: #38
(they are cross-referenced, so we won't loose the discussion thread here)

from architecture.