![]() The next line two lines indicate that no issues were found, but this is where any issues will be In the case of the precedingĮxample, the progam is checking against the requirements of EPUB 3.2. The first line specifies what version of EPUB is being validated. Messages: 0 fatals / 0 errors / 0 warnings / 0 infos If EPUBCheck does not detect any problems, it will emit a series of messages like the following: Validating using EPUB version 3.2 rules. The rest of the examples on this page for readability purposes. The following is an example of how EPUBCheck could be called from the command line to validate theĪccessible_epub_3.epub file: > java -jar c:\epubcheck\epubcheck.jar c:\epubs\accessible_epub_3.epubįull paths to the epubcheck.jar file and publication to be checked are omitted from The full path to the file has to be specified if it is not in the same publication.epub - The second argument is the name of the packaged EPUB.To reference this file depends on where EPUBCheck is installed and what directory EPUBCheck is ![]() Jar file ( epubcheck.jar) that contains the EPUBCheck program. -jar path\to\epubcheck.jar - The first argument is a reference to the Java.The command to run EPUBCheck is the same regardless of the operating system used. The following command will change the command line interface to the c:\epubs TheĬd command is used to change the directory. Where the publication to be validated is located to avoid entering lengthy file paths. When starting a new command-line interface, the starting directory is usually listed before the inputĪlthough EPUBCheck can be run from almost any directory, it is often simpler to change directories to ( powershell.exe) can be used to run EPUBCheck. On Windows, both the Command Prompt ( cmd.exe) and PowerShell Which interface to use depends on the operating The EPUBCheck program is written as a Java library, so running it requires some basic knowledge ofĮntering instructions from a command-line interface. That are in violation of the requirements of the standard and/or that could cause a publication not Tool that automatically checks EPUB publications for conformance to the standard. Getting StartedĮPUBCheck is a free command-line validation See the details in the list of issues closed since the last public release.Instructions on how to obtain and configure a system to run EPUBCheck are available from the EPUBCheck Usage wiki This page does notĬover installation issues. #711 – Bugfix for false positive error messages due to locale settings #686 – Make BitmapChecker.ImageHeuristics a public object ![]() ![]() #678 – Clarify ACC-009 message: 'alt' -> 'alttext' attribute #689 – Fix for unclosed ImageInputStreams on image file validation #657 – New method Archive.createArchive(File) to specify file paths when using this in 3rd party toolsįix for critical vulnerability CVE-2016-9487 #670 – Fix illegal characters in XML output #517 – Include list of all resources media types Special thanks to Craig Arendt for having identified the vulnerability and disclosed it privately to EpubCheck's team. This version includes a fix for a critical security vulnerability (CVE-2016-9487) which may, under some circumstances, enable a remote attacker to access arbitrary files on the system where EpubCheck is running.Īll users should update to EpubCheck 4.0.2 as soon as possible. EpubCheck 4.0.2 is a maintenance release of the EPUB conformance checker.
0 Comments
Leave a Reply. |