Download EPUB-Checker - Check EPUB files for errors or warnings, validate them and also export the log text with this simple and user-friendly software. Standalone "EPUB-Checker" application for Windows, Mac OS and Linux repo/ com · moved the "scope system" libraries to a local in-repo maven repositor. Validation tool for EPUB. Contribute to w3c/epubcheck development by creating an account on GitHub.
|Language:||English, Spanish, Arabic|
|Genre:||Children & Youth|
|ePub File Size:||20.85 MB|
|PDF File Size:||8.12 MB|
|Distribution:||Free* [*Sign up for free]|
Submit an EPUB document for validation. Your file must This site uses EPUBCheck to provide validation information for EPUB 2 and 3 documents. If you are. Use this epub validator tool by uploading your portal7.info file for validation according to epubcheck version No registration required. ePUB Validator - ePUB Validator is a handy utlity designed to enable you to check your ePub files. ePUB Validator is a GUI front-end for EpubCheck. You can .
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together. If nothing happens, download GitHub Desktop and try again. If nothing happens, download Xcode and try again. If nothing happens, download the GitHub extension for Visual Studio and try again. Please visit our website https: Our app and code and all the java sources in de. Therefore, this part will only work on one of our company Mac's.
Listing 2. Sample container. These topics are not covered in this tutorial.
See the OCF specification for more information. The mimetype and container files are the only two whose location in the EPUB archive are strictly controlled.
As recommended although not required , store the remaining files in the EPUB in a sub-directory. The following section of this tutorial covers the files that go into OEBPS—the real meat of the digital book: its metadata and its pages.
Open Packaging Format metadata file Although this file can be named anything, the OPF file is conventionally called content. It specifies the location of all the content of the book, from its text to other media such as images. Listing 3. Metadata Dublin Core defines a set of common metadata terms that you can use to describe a wide variety of digital materials; it's not part of the EPUB specification itself.
Any of these terms are allowed in the OPF metadata section. When you build an EPUB for distribution, include as much detail as you can here, although the extract provided in Listing 4 is sufficient to start. Listing 4. Extract of OPF metadata The two required terms are title and identifier. According to the EPUB specification, the identifier must be a unique value, although it's up to the digital book creator to define that unique value.
Note that the value of the attribute unique-identifier must match the ID attribute of the dc:identifier element. Other metadata to consider adding, if it's relevant to your content, include: Language as dc:language.
Publication date as dc:date.
Publisher as dc:publisher. This can be your company or individual name. Copyright information as dc:rights. Including a meta element with the name attribute containing cover is not part of the EPUB specification directly, but is a recommended way to make cover pages and images more portable.
This example shows both forms. The value of the meta element's content attribute should be the ID of the book's cover image in the manifest, which is the next part of the OPF file.
This usually means a list of XHTML files that make up the text of the eBook plus some number of related media such as images.
Every file that goes into your digital book must be listed in the manifest. Listing 5 shows the extracted manifest section. Listing 5. Extract of OPF manifest You must include the first item, toc. You can include non-supported file types if you provide a fall-back to a core type. See the OPF specification for more information on fall-back items. This is easy to confuse with the reference to the OPF file in the container. Spine Although the manifest tells the EPUB reader which files are part of the archive, the spine indicates the order in which they appear, or—in EPUB terms—the linear reading order of the digital book.
One way to think of the OPF spine is that it defines the order of the "pages" of the book. The spine is read in document order, from top to bottom.
Listing 6 shows an extract from the OPF file. Listing 6. Extract of OPF spine Each itemref element has a required attribute idref, which must match one of the IDs in the manifest. The toc attribute is also required.
The linear attribute in the spine indicates whether the item is considered part of the linear reading order versus being extraneous front- or end-matter. Guide The last part of the OPF content file is the guide.
This section is optional but recommended. Listing 7 shows an extract from a guide file. Listing 7. Extract of an OPF guide The guide is a way of providing semantic information to an EPUB reading system. While the manifest defines the physical resources in the EPUB and the spine provides information about their order, the guide explains what the sections mean. Here's a partial list of the values that are allowed in the OPF guide: cover: The book cover title-page: A page with author and publisher information toc: The table of contents For a complete list, see the OPF 2.
This is rarely a problem when you generate EPUBs programmatically, where the same code can output to two different files. Take care to put the same information in both places, as different EPUB readers might use the values from one or the other. Although the OCF file is defined as part of EPUB itself, the last major metadata file is borrowed from a different digital book standard.
DAISY is a consortium that develops data formats for readers who are unable to use traditional books, often because of visual impairments or the inability to manipulate printed works. The NCX defines the table of contents of the digital book. In complex books, it is typically hierarchical, containing nested parts, chapters, and sections. Listing 8. This element should match the dc:identifier in the OPF file.
This example has only one level, so this value is 1. It's okay to be confused, as both files describe the order and contents of the document.
The easiest way to explain the difference is through analogy with a printed book: The OPF spine describes how the sections of the book are physically bound together, such that turning a page at the end of one chapter reveals the first page of the second chapter.
The NCX describes the table of contents at the beginning of the book. The table of contents always includes all the major sections of the book, but it might also list sub-sections that don't occur on their own pages. The navMap is the most important part of the NCX file, as it defines the table of contents for the actual book.
The navMap contains one or more navPoint elements. Each navPoint must contain the following elements: A playOrder attribute, which reflects the reading order of the document. This follows the same order as the list of itemref elements in the OPF spine. This is typically a chapter title or number, such as "Chapter One," or—as in this example—"Cover page.
This will be a file declared in the OPF manifest. It is also acceptable to use fragment identifiers here to point to anchors within XHTML content—for example, content. Optionally, one or more child navPoint elements. Nested points are how hierarchical documents are expressed in the NCX. The structure of the sample book is simple: It has only two pages, and they are not nested. That means that you'll have two navPoint elements with ascending playOrder values, starting at 1.
In the NCX, you have the opportunity to name these sections, allowing readers to jump into different parts of the eBook. Adding the final content Now you know all the metadata required in EPUB, so it's time to put in the actual book content. You can use the sample content provided in Downloadable resources or create your own, as long as the file names match the metadata.
Next, create these files and folder: title. This file can contain any CSS declarations you like, such as setting the font-face or text color. See Listing 10 for an example of such a CSS file.
Use this sample for your title page title. Listing 9. Sample title page title. Therefore, this part will only work on one of our company Mac's. To be able to build packages on other Mac systems or on Windows, just skip the codesigning task with the following option:. Skip to content. Dismiss Join GitHub today GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign up. Find File. Download ZIP.
Sign in Sign up. Launching GitHub Desktop Go back. Launching Xcode Launching Visual Studio Erhan Uzumcu! Latest commit 2fefd03 May 24, Download Please visit our website https: This is just the source code repository.
You won't find any binary downloads here License information Our app and code and all the java sources in de.