-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RSC-007: also print the missing reference in the error message #720
Labels
type: duplicate
The issue duplicates an existing issue
Comments
tofi86
added
the
type: improvement
The issue suggests an improvement of an existing feature
label
Dec 17, 2016
tofi86
added
type: duplicate
The issue duplicates an existing issue
and removed
type: improvement
The issue suggests an improvement of an existing feature
labels
Dec 18, 2016
tofi86
added a commit
that referenced
this issue
Dec 18, 2016
rdeltour
pushed a commit
that referenced
this issue
Dec 20, 2016
Fixed in PR #722 |
tofi86
added a commit
that referenced
this issue
Dec 21, 2016
for RSC-007 this has already been done with 71a76ee
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're and our customers are checking hundreds of EPUBs a month and lot's of people stumble upon the error
RSC_007 (Referenced resource could not be found in the EPUB.)
as it doesn't provide the referenced resource in the error message.Yes, the message does provide a location (file, line, col), but normal users are mostly not able to open the EPUB file and locate the error. However, if the missing resource name (only the name, not the path) would be part of the error message, it would be easier for normal users to locate the missing resource in either the EPUB file or the source XML.
The text was updated successfully, but these errors were encountered: