View Single Post
Old 07-19-2021, 08:52 AM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,605
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
It's probably the case of the 'images' folder in the href. Make sure the image is really in an 'images' folder, and not, in fact, an 'Images' folder. It shows up in Preview because Windows doesn't use a case-sensitive file system. But many devices the book needs to work on, will. Hence the validation errors.

The seemingly contradictory flightcrew warning/error are quite consistent with such a scenario. Since the two paths don't actually match, Flightcrew believes it's dealing with two separate resources: one referenced in the opf manifest (but not found in the xhtml) and one found in the xhtml href (but not manifested in the opf)

Last edited by DiapDealer; 07-19-2021 at 09:10 AM.
DiapDealer is offline   Reply With Quote