Skip to content

Readium is unable to open (guided navigation) files inside of an epub with a space in the title #94

@tefkah

Description

@tefkah

Readium-cli version: 0.6.1

This is related to this issue users from Storyteller experience: https://gitlab.com/storyteller-platform/storyteller/-/issues/376

For a file eg Death Masks_split_000.html, it seems impossible to request it from the readium server.

eg

GET http://localhost:9000/webpub/xxxxxx/Death%20Masks_split_000.html

returns

404 resource: error 404: file does not exist

Interestingly, the twice encoded version Death%2520Masks_split_000.html does not return the error message, but does return a 404

The same is true for guided navigation documents.

I do know that in the Epub 3.3 spec section 4.2.3 it says

For compatibility with older reading systems, file names SHOULD NOT contain SPACE (U+0020) characters.

See discussion: w3c/epub-specs#2458

But it's not a MUST, so I think it would be nice if this was possible! (im not a spec person, so if i'm interpreting the distinction between MUST and SHOULD here incorrectly, totally possible!)

It may also be possible that there is some way of encoding spaces that will make Readium accept them, but I haven't yet found it!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions