- #COULD NOT START THE EPUB CHECKER ARCHIVE#
- #COULD NOT START THE EPUB CHECKER FULL#
- #COULD NOT START THE EPUB CHECKER CODE#
- #COULD NOT START THE EPUB CHECKER ZIP#
Property "FontName" of type STRING and arity SCALAR.Property "Font" of type PROPERTY and arity SET.Property "Fonts" of type PROPERTY and arity SET.Property "Rights" of type PROPERTY and arity SCALAR.Property "Subject" of type STRING and arity ARRAY.Property "Publisher" of type PROPERTY and arity SCALAR.Property "Date" of type LONG and arity SCALAR.Property "Contributor" of type STRING and arity ARRAY.Property "Creator" of type STRING and arity ARRAY.Property "Title" of type STRING and arity ARRAY.Property "Identifier" of type STRING and arity SCALAR.Property "Info" of type PROPERTY and arity SET.Property "Language" of type STRING and arity SCALAR.Property "CharacterCount" of type LONG and arity SCALAR.Property "PageCount" of type LONG and arity SCALAR.Property "EPUBMetadata" of type PROPERTY and arity LIST.Representation information, the following The MIME type is reported as: application/epub+zip As mentioned in the previous section, the exception is package ERRORs (PKG-*), which will always result in a "Not Well Formed" assignment. If the EPUB has a status of "Well Formed", but contains one or more message with a severity level of "ERROR" the EPUB is labelled as "Not Valid". All files referenced in the OPF must be present in the package and have valid file namesĪs with the "Well Formed" status, the criteria that determine "Validity" are based on the messages output by the EPUBCheck module.The package must contain a META-INF/container.xml file.The package must contain an OPF XML file.The EPUB and each of the files within it must not be corrupted.There must be "PK" at byte 0, "mimetype" at byte 30, and "application/epub+zip" at byte 38.
#COULD NOT START THE EPUB CHECKER FULL#
For the full list, please refer to the EPUBCheck messages link provided above: The following are some of the key criteria that must be met for an EPUB object to be considered Well Formed in the JHOVE report. it is a package-related message (starts with "PKG-") with a severity level of ERROR.A message will cause a status of "Not Well Formed" if either: In addition to this list, an undefined failure within the EPUBCheck module will report as a FATAL error - this happens if a non-EPUB file is passed into the module, for example.
#COULD NOT START THE EPUB CHECKER CODE#
The JHOVE report outputs the messages as provided by EPUBCheck - a full list of these can be seen in the EPUBCheck code base.
#COULD NOT START THE EPUB CHECKER ARCHIVE#
Well formed status is based on evaluation of both the archive file as a whole and on the presence of specific files within it.
#COULD NOT START THE EPUB CHECKER ZIP#
Additional metadata provided as properties in the report (detailed below) will indicate the presence of features that may be dependent on the e-book software's support for them.ĮPUBs are a form of ZIP archive file. To clarify, all EPUB2s will validate as 2.0.1 and all EPUB3s as 3.2 until a new EPUB version is released along with an updated EPUBCheck tool. The EPUBCheck tool will validate the file against the specification of the most recent point release associated with that major version - and it is this number that will appear as the "version" in the JHOVE report. This is based on the "version" property on the "package" tag within the OPF XML. Important note: The internal EPUB metadata only reveals its major version - which is currently either EPUB2 or EPUB3. The EPUB-ptc module recognizes and validates the following public profiles:
Visit the EPUB Specifications and Projects page for more information on the EPUB format. The EPUB-ptc JHOVE module is a wrapper around the official EPUBCheck tool. The EPUB-ptc module recognizes and validates the EPUB format.
0 kommentar(er)
