View Single Post
Old 02-21-2026, 05:45 PM   #11
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 9,409
Karma: 6733754
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by Doitsu View Post
The official Apple Books Asset Guide 5.3.1 doesn't explicitly mention any folder restrictions. Maybe they assume that every ebook has the same structure as the sample image?
I just tested taking that same epub and only moving the content.opf out of the OEBPS folder up to root. Then saved it.

There are now no manifest hrefs that start with "../".

Now Books.app opened it and the text was readable just fine.

So I guess iBooks (Books) is allowing **almost** every structure as long as the opf manifest hrefs do not start with "../".

Probably a very good security move for unknown epubs by any e-reader. And important for developers/publishers of epubs to know.

Last edited by KevinH; 02-21-2026 at 06:04 PM.
KevinH is offline   Reply With Quote