EpubCCEPUBCheck RSC-017: parser warning in a file
Updated:
EPUBCheck RSC-017 is a warning message: “Warning while parsing file: ….” The parser found something questionable that does not stop it from reading the file. It is a warning: the EPUB stays valid, but the text after the colon often points at a real mistake.
The official message
Warning while parsing file: %1$s
- Default severity
- Warning. The EPUB is still valid, but something is likely to cause problems in some reading apps. EPUBCheck exits with 0 unless you pass --failonwarnings.
- EPUBCheck version
- 5.4.0
%1$s, %2$s… are filled in with the file, value or element EPUBCheck found.
Typical causes
- Constructs that are allowed but discouraged or suspicious; the text after the colon names it.
- Markup copied from web pages that relies on browser leniency.
How to fix it
- Read the text after the colon: EPUBCheck reports the file, the line and column, and the parser's own description of the problem.
- Fix it if the message points at a real mistake; it does not make the EPUB invalid on its own.
- Validate again to check that no related error was hiding behind it.
When it's not this
A schema error that makes the file invalid is RSC-005; a file that cannot be parsed is RSC-016.
Terms used here
Other RSC messages
RSC-016Fatal Error while parsing file: …RSC-015A fragment identifier is required for svg use tag references.RSC-019EPUBs with Multiple Renditions should contain a META-INF/metadata.xml file.RSC-014Fragment identifier defines an incompatible resource type.RSC-020"…" is not a valid URL (…)RSC-013Fragment identifier is used in a reference to a stylesheet resource.
Sources
Message text and severity from EPUBCheck 5.4.0 (W3C, BSD-3-Clause). Explanation by EpubCC.