w3c/epub-specs

Character restrictions don't apply to file paths?

Closed this issue · 2 comments

Is it correct that you can use any characters you want in file paths with the only restrictions on file names?

Seems odd, although we can't just add file paths without separating out solidus and reverse solidus.

FWIW, EPUBCheck currently enforces the restrictions on both paths and names…

Looks like I should have checked the definitions closer. File name also encompasses directory name, so the path is covered by extension. Closing as invalid.