You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LPF relies on zip, and zip is not precise at all on this subject. This is why we ended up with this note:
The zip specification has few constraints on the characters allowed for file and directory names. When crafting such names, authors must be careful to use characters which allow a broad interoperability among operating systems
Activity
dauwhe commentedon Feb 26, 2021
U+FFFE and U+FFFF are already forbidden, as are U+FFFFE, U+FFFFF, U+10FFFE, and U+10FFFF.
So I guess that leaves 28 more non-characters to forbid?
Don't make me create tests for all of this!
iherman commentedon Mar 3, 2021
@llemeurfr you probably looked into this when you edited the LPF document... any help on this?
llemeurfr commentedon Mar 3, 2021
LPF relies on zip, and zip is not precise at all on this subject. This is why we ended up with this note:
The zip specification has few constraints on the characters allowed for file and directory names. When crafting such names, authors must be careful to use characters which allow a broad interoperability among operating systems
iherman commentedon Mar 3, 2021
At the end of the day, EPUB also relies on Zip, doesn't it? So we may have to do the same and that is that...