search

1080linebooks / sigil

Automatically exported from code.google.com/p/sigil
GNU General Public License v3.0
0 stars 0 forks source link

Error results use nonexistant paths. #849

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open an ePub file that doesn't use paths like OEBPS, Fonts, Images, etc. but 
has some errors.
2. Validate it.
3. Note that the paths which come up do not match the paths in the document.

What is the expected output? What do you see instead?
I expect to see errors relating to paths which actually exist in the zip file.

What version of the product are you using? On what operating system?
Sigil 0.4.0 on Windows XP SP3.

Original issue reported on code.google.com by bentraff...@gmail.com on 12 Apr 2011 at 7:49

GoogleCodeExporter commented 9 years ago 
Attach the epub file which exhibits the problem.

Original comment by Strahinja.Markovic@gmail.com on 16 Apr 2011 at 8:23

GoogleCodeExporter commented 9 years ago 
A sample ePub that demonstrates the issue is attached. I've also attached three 
screenshots with the behavior circled in red.

Original comment by bentraff...@gmail.com on 16 Apr 2011 at 8:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Now I understand. Your epub uses a different file structure than what Sigil 
uses internally, and you want errors reported against your original structure?

You can't do that in Sigil. When you open a book, it rearranges the epub 
structure.

But if you just want the validator, get the separate FlightCrew GUI application 
(http://code.google.com/p/flightcrew/). FC is the validator used in Sigil. The 
standalone version of FC will report errors against you original structure 
(since there is no epub import process, like there is in Sigil).

Original comment by Strahinja.Markovic@gmail.com on 16 Apr 2011 at 8:50

GoogleCodeExporter commented 9 years ago 
That's a really confusing way to report errors when validating. Wouldn't it 
make more sense to report the errors against the actual structure of the 
document? I don't understand the logic behind re-organizing the document 
dynamically.

Original comment by bentraff...@gmail.com on 16 Apr 2011 at 8:57

GoogleCodeExporter commented 9 years ago 
The reasons are many and it would take too long to explain.

If you want errors reported against the original structure, use standalone 
FlightCrew.

Original comment by Strahinja.Markovic@gmail.com on 16 Apr 2011 at 9:32