Closed GoogleCodeExporter closed 8 years ago
Actually FlightCrew is correct here. If you reference a website without the
"http://" part, you're referencing a local file. In your example, you're
referencing a file called "www.website.com" in the folder of the XHTML file.
That file could realistically exist. Since it doesn't, FC reports an error.
The fact that it is a malformed hyperlink is altogether irrelevant. "bit.ly"
would be a malformed link, but that's another file that could actually exist.
Bottom line, there is no way in which FC could know that what you're
referencing is not a local file but is a malformed link, since without the
scheme you have a relative URL. It can only report it as a missing file, since
that's what the specs say that a relative URL is supposed to be interpreted as.
Original comment by Strahinja.Markovic@gmail.com
on 12 Nov 2010 at 1:18
Ah ok. Then its a bit hard to differentiate between a actual file present in
the ePub but not linked to the content (fe an unused image) and a link in the
content to a file that is not present in the ePUB. (If you know what I mean)
Thankf for the clarification.
Original comment by albar...@gmail.com
on 12 Nov 2010 at 6:19
Original issue reported on code.google.com by
albar...@gmail.com
on 12 Nov 2010 at 3:05