Where is the image location alias found in epubs?

philja · Yesterday, 03:19 PM

I have three epub2 's to edit where the owner wants to improve the alt=" " for the images, amongst other changes.

The first thing I noticed was the way the images were coded in the xhtml files:

Code:

<img class="x65" src="Pictures/image1.gif" alt=" "/>

The images all appear conventionally in a folder named 'Images' in the Book Browser, and usually I find images in Code View like this:

Code:

<img class="x65" src="../Images/image1.gif" alt=" "/>

In the other two epubs, instead of 'Pictures', the images have src="images/image1.gif"

When I open most epubs in an archive viewer, there is the usual structure of a META-INF folder, an OEBPS folder, and a mimetype file. Inside the OEBPS folder, we find the Images, Text, Styles ... folders + the content.opf and ncx files.

When I examine these three epubs the same way, there is the META-INF folder, a Pictures (or images) folder (containing all the images), and all the text files are at the same level as the mimetype and content.opf file. There is no OEBPS folder.

They all pass the F7 and epubcheck tests ok.

I'm just curious - the images all display ok. Are these epubs the product of a particular conversion application?

DiapDealer · Yesterday, 05:46 PM

There is no specification for how epubs need to be structured. As long as the paths/links are valid, things will still work. Some applications have been known to create a completely flat epub structure. Some create other structures. Sigil USED to force its proprietary structure on every epub it opened/saved, but it hasn't done that for a a long time. Many people became used to that structure.

The "Restructure to Sigil Norm" tool will restructure the epubs to the folder hierarchy many expect, but it's not at all required.

DNSB · Yesterday, 11:46 PM

I still use the Restructure tool but that is due to having gotten used to finding images in Images, etc. Old dogs and an adversion to new tricks.

Actually, there are a few rules for ePub structure. The mimetype file is required, must be in the root of the container and must be stored uncompressed. The container.xml file is required and must be stored in a META-INF directory in the root of the container. There are several other optional xml files (encryption.xml (required if obfuscation/encryption is used), manifest.xml, metadata.xml, rights.xml & signatures.xml). You will also commonly find that Apple and Kobo xml files are stored in the META-INF file though this is not required (com.apple.ibooks.display-options.xml & com.kobobooks.display-options.xml) and can cause an error message if they are also listed in the .opf file.

Yesterday, 03:19 PM	#1
philja Evangelist Posts: 418 Karma: 100100 Join Date: Nov 2015 Location: Europe EEC Device: Kindle Fire HD6 & HD8	Why are some epubs without OEBPS folders? I have three epub2 's to edit where the owner wants to improve the alt=" " for the images, amongst other changes. The first thing I noticed was the way the images were coded in the xhtml files: Code: <img class="x65" src="Pictures/image1.gif" alt=" "/> The images all appear conventionally in a folder named 'Images' in the Book Browser, and usually I find images in Code View like this: Code: <img class="x65" src="../Images/image1.gif" alt=" "/> In the other two epubs, instead of 'Pictures', the images have src="images/image1.gif" When I open most epubs in an archive viewer, there is the usual structure of a META-INF folder, an OEBPS folder, and a mimetype file. Inside the OEBPS folder, we find the Images, Text, Styles ... folders + the content.opf and ncx files. When I examine these three epubs the same way, there is the META-INF folder, a Pictures (or images) folder (containing all the images), and all the text files are at the same level as the mimetype and content.opf file. There is no OEBPS folder. They all pass the F7 and epubcheck tests ok. I'm just curious - the images all display ok. Are these epubs the product of a particular conversion application? Last edited by philja; Yesterday at 04:27 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Likebook Mars - Power Off Image Location?	thatguyatdennys	Boyue	2	03-05-2019 08:31 PM
Aura Keeping annotations when moving .epubs location	MicheleBS	Kobo Reader	7	12-28-2017 10:22 AM
Image Not Found	jackibar	Sigil	2	10-18-2013 10:48 AM
(PW) Location of waterstones screensaver image	mrspaceman	Kindle Developer's Corner	19	05-09-2013 02:07 AM
Request Location of e-ink image shown when power is off	sanketsu	enTourage eDGe	20	12-18-2011 05:06 AM

Yesterday, 05:46 PM	#2
DiapDealer Grand Sorcerer Posts: 29,699 Karma: 212474403 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	There is no specification for how epubs need to be structured. As long as the paths/links are valid, things will still work. Some applications have been known to create a completely flat epub structure. Some create other structures. Sigil USED to force its proprietary structure on every epub it opened/saved, but it hasn't done that for a a long time. Many people became used to that structure. The "Restructure to Sigil Norm" tool will restructure the epubs to the folder hierarchy many expect, but it's not at all required.

Yesterday, 11:46 PM	#3
DNSB Bibliophagist Posts: 54,165 Karma: 182150349 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	I still use the Restructure tool but that is due to having gotten used to finding images in Images, etc. Old dogs and an adversion to new tricks. Actually, there are a few rules for ePub structure. The mimetype file is required, must be in the root of the container and must be stored uncompressed. The container.xml file is required and must be stored in a META-INF directory in the root of the container. There are several other optional xml files (encryption.xml (required if obfuscation/encryption is used), manifest.xml, metadata.xml, rights.xml & signatures.xml). You will also commonly find that Apple and Kobo xml files are stored in the META-INF file though this is not required (com.apple.ibooks.display-options.xml & com.kobobooks.display-options.xml) and can cause an error message if they are also listed in the .opf file.

Advert