View Single Post
Old 09-25-2016, 12:41 PM   #6
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,410
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by davidfor View Post
The "OEBPS" directory is so common, I was wondering if it was part of the standard. It doesn't seem to be, but every recommendation I found for the structure had it, so it the way everyone codes it.
As far as I recall, the specification says the mimetype file must be in the root directory of the epub file structure and the container.xml file must in a META-INF directory in the root. The rest of the directory structure is found from the content.opf file found at the path in the container.xml file. So no requirement for the OEBPS directory though most publishing software does use it. The epub3 OCF standard does say "It is recommended that the contents of the EPUB Publication be stored within its own dedicated directory under the container's root." while the epub2 OCF standard said much the same in a wordier fashion.

Last edited by DNSB; 09-25-2016 at 12:52 PM. Reason: Hmmm... epub4? Should have been epub3.
DNSB is offline   Reply With Quote