This resource is reachable but not present in the OPF <manifest>.

[wannabee]

Hi

Flightcrew gives me the following warning
This resource is reachable but not present in the OPF <manifest>.

In the past I had simialr warnings for fonts but as readers substitute fonts when necessary I ignored the warning.

However this warning for the TEXT folder that Sigil created while I was making a TOC baffles me. (Well I presume it's the TEXT folder Sigil created that Flightcrew has picked up on.) Is it a warning that MUST be addressed?

[Toxaris]

I have this error sometimes when there is a reference to a footnote or something missing. A link to an footnote, where the file which contains the footnotes is not specified.

However, looking at the error, I think there is an another error in place. There is a reference to the file 'tired -but-not-sleeping.epub', where I think you mean 'tired-but-not-sleeping.epub'. I think you have a space somewhere in a link.

[Adjust]

I doubt it...since you can have spaces in the "file name.epub" file, which seems to be what that is referencing.

@Wannabee, do all the link references in the manifest link to the newly created /text directory (as in images, xhtml files etc)

[theducks]

That error indicate there is a line somewhere on one of the pages that has no file name associated with the HREF
"../Text/#foo" is what I usually find. foo is a local anchor name), that lost (or never had) it's file name portion.
It happens, but I have not found a repeatable case to submit

[Toxaris]

That's what I meant... I do have that now and then when I split files with endnotes. Unfortunatly I cannot repeat it either...

[Adjust]

Interesting. Because I get the "Fo" everytime I convert an InDesign CS5 back to CS3 without linking the image first... The .INX file screws up the path, but you link the images FIRST before converting to .inx then all is good...

Strange that it appears in the OPF file though

[theducks]

Originally Posted by Adjust

Interesting. Because I get the "Fo" everytime I convert an InDesign CS5 back to CS3 without linking the image first... The .INX file screws up the path, but you link the images FIRST before converting to .inx then all is good...

Strange that it appears in the OPF file though

I think you are mis-interpreting the message
It says the a page references the no-file-name anchor AND there is no ENTRY in the OPF for a file with no-file-name

What I dont undestand is why FC does not show the line number for the reference . (Is it a simple case, that a nil filename condition was not handled?)

[Adjust]

Deeeerrrrr, of course you are correct. I'm such an idiot sometimes...

Maybe he runs it through epubcheck so that it give a line number???

[Toxaris]

Well, you could search the code view for '../Text/#'. That would give the culprit.

[wannabee]

Originally Posted by Adjust

@Wannabee, do all the link references in the manifest link to the newly created /text directory (as in images, xhtml files etc)

@Adjust - Yep, I'm at home but from memory Sigil rearranged the standard InDesign directory from OPEF with only IMAGES folder to STYLES, TEXT, IMAGES and maybe some other folders as well. (Sorry, it's the first time I used Sigil for a TOC because CS5 wouldn't make an ePub from the file if I selected TOC styles on. Anyway I'm pretty sure it was .../text/filename.xhtml for all the files.
CS5 hung every time I tried to include it's TOC. Maybe that's the culprit?

Originally Posted by theducks

That error indicate there is a line somewhere on one of the pages that has no file name associated with the HREF
"../Text/#foo" is what I usually find. foo is a local anchor name), that lost (or never had) it's file name portion.
It happens, but I have not found a repeatable case to submit

@theducks - Are you kidding me? you must have seen so many errors in your life to come to a conclusion like that from the little info I gave you. Is your middle name Sherlock? I've never seen a foo except on a graffitied wall but I'll certainly do a search.

Originally Posted by Toxaris

That's what I meant... I do have that now and then when I split files with endnotes. Unfortunatly I cannot repeat it either...

@Toxaris - I presume you split files in SIgil.....and that's when you have the same message?

Originally Posted by Adjust

Interesting. Because I get the "Fo" everytime I convert an InDesign CS5 back to CS3 without linking the image first... The .INX file screws up the path, but you link the images FIRST before converting to .inx then all is good...

Strange that it appears in the OPF file though

@Adjust - CS5 to CS3 via INX sounds outside my capabilities unless there's a CS4 conversion as well between IDXL (CS5) and INX (CS3). Am I wrong? ( I know it's a bit off topic but I have CS2 at home and......never the two shall meet!)

Originally Posted by theducks

I think you are mis-interpreting the message
It says the a page references the no-file-name anchor AND there is no ENTRY in the OPF for a file with no-file-name

What I dont undestand is why FC does not show the line number for the reference . (Is it a simple case, that a nil filename condition was not handled?)

@theducks - thats what I thought it meant, but that means Sigil somehow missed something while rewriting them.

Remember, When I tried to export this InDesign file to ePub it hung unless I exported it without InDesign's TOC.

HAS THAT HAPPENED TO ANYONE ELSE YOU KNOW?

I'll check all the Paragraph Styles tomorrow because I'm working from a file for print I inherited from another designer. (Just so you know I'm not a complete dill, I did rework the styles for the eBook before this. Though this is the second time it's happened to me. I could not export to ePub with the InDesign TOC - but could without it. Hence the use of Sigil to create a TOC)

Originally Posted by Toxaris

Well, you could search the code view for '../Text/#'. That would give the culprit.

I love this site and you guys for all the help. AND I get quite a bit of help from (not to be left out) the gals on this site as well.
I'll report back. Thanks

[DMSmillie]

Originally Posted by wannabee

I love this site and you guys for all the help. AND I get quite a bit of help from (not to be left out) the gals on this site as well.

Hah!



~~~~~
This resource is reachable but not present in the OPF <manifest>

I understood that to indicate that there's a file (HTML or image) contained in the EPUB that isn't listed in the OPF file <manifest> section?

[Dillinquent]

Flightcrew gives me the following warning
This resource is reachable but not present in the OPF <manifest>.

Broken hyperlinks do that, usually where the 'http://' is missing in a web URL

[wannabee]

ERROR: tired -of-not-sleeping.epub/OEBPS/Text/Section0008.xhtml(250): 'x53-respiratory-anchor': fragment identifier is not defined in 'OEBPS/Text/Tired-of-not-sleeping.xhtml'

ePub check found heaps of these errors.
It was my first attempt to make a TOC in Sigil because InDesign CS5 hung whenever I ticked the "Include InDesign TOC entries" box.
I exported it to CS4 and made a perfectly good epub from there.
That's the second time it's happened and I can't narrow it down to anything. I can't see any kind of conflict in the paragraph styles.

[Adjust]

Take a look at this.
https://www.mobileread.com/forums/sho...light=fragment

[Toxaris]

Originally Posted by wannabee

@Toxaris - I presume you split files in SIgil.....and that's when you have the same message?

Yes, however it is not consistent. Usually it works without a problem, but sometimes it happens. No clue why it doesn't work sometimes. Since I cannot make a case that will give the same result every time, I cannot create an issue on the tracker. Bug hunting is really difficult when there is no repeatable case.