Git Product home page Git Product logo

epub3-samples's Introduction

EPUB 3 Samples

This repository contains the source for a variety of EPUB 3 sample documents. The collection is intended to showcase features of the EPUB standard, and to provide testing materials for Reading System developers. It is maintained by the W3C's EPUB 3 Community Group.

For quick access to the samples, please see the samples table and feature matrix.

Please see the project page for more general information about the samples.

Licensing

Unless specified otherwise in the sample table, all samples are licensed under CC-BY-SA 3.0

Compiling

All of the latest samples are available for download from the sample table.

If needed, you can also create EPUB publications directly from the samples source. There are two sets of shell and batch scripts available at the root of the repository.

The first, pack-all, will build all of the samples:

pack-all.sh

The second script, pack-single, is used to build individual samples:

pack-single.sh 30/accessible_epub_3

The argument to this script is the relative path to the sample you want to build.

Note: The batch script can be run on Windows OSes; there is no difference in functionality or how it is called.

Want to contribute?

If you want to contribute to this project, there are several options:

Reporting Issues

We want to make sure all samples provided here are conformant, pristine, and employ best practices consistently. If you spot an issue while reviewing and/or testing the content, report it to the issue tracker.

Contributing new samples

If you want to contribute sample(s), please contact the project owners. After an initial discussion, they will either give you write access to the repository, or arrange some other means of getting the content into the repository. Note that all submitted content is by default subject to CC-BY-SA 3.0 licensing.

This site does not list attribution for samples. As a contributor, you may specify attribution metadata only within the submitted EPUB Publication.

Note also that the project owners may suggest or even require modifications to your submissions to be done in order to meet the desired quality level.

Contributing variations / improvements to existing samples

If you want to contribute to an existing sample by adding to or varying some aspect of it, use the issue tracker and submit your patch as an attachment. Note that your submission must adhere to the same open source license as the containing sample.

epub3-samples's People

Contributors

dauwhe avatar i49 avatar lizadaly avatar marisademeglio avatar mattgarrish avatar murata2makoto avatar nikolas avatar vincent-gros avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

epub3-samples's Issues

Invalid pageTarget type value?

The NCX file for the ePub 3 samples uses the XML Namespace at http://www.daisy.org/z3986/2005/ncx/

This says the following about the pageTarget element:

<!-- Revised, 3/31/2004:  Added pageTarget element -->
<!-- Revised, 4/5/2004:  Added description of value attribute to comment -->
<!-- Page Target -  Container for 
  text, audio, image, and content elements containing navigational 
  information for pages.  The "value" attribute is a positive integer representing 
the numeric value associated with a page. Combination of values of type and 
value attributes must be unique, when value attribute is present. 
-->
<!ELEMENT pageTarget (navLabel+, content)>
<!-- Revised, 4/5/2004:  Added class attribute -->
<!-- Revised, 4/5/2004:  Changed declaration of type attribute to enumerate values -->
<!-- Revised, 4/5/2004:  Added playOrder -->
<!ATTLIST pageTarget
   id       ID          #IMPLIED
   value    CDATA       #IMPLIED
   type     (front | normal | special)       #REQUIRED
   class    CDATA       #IMPLIED
   playOrder CDATA      #REQUIRED
>

If I'm reading this correctly, the only permitted values for the pageTarget's type attribute are front, normal, and special.

Some of the examples listed in this repository use values other than these. Using https://github.com/IDPF/epub3-samples/blob/master/30/childrens-literature/EPUB/toc.ncx as an example:

		<pageTarget type="body">
			<navLabel>
				<text>169</text>
			</navLabel>
			<content src="s04.xhtml#Page_169"/>
		</pageTarget>

Is my interpretation of the spec correct? What is the meaning of the "body" pageTarget type?

Pagebreak in Children's Literature

In the Children's Literature example, the page break for pages 197, 212, 229 and 255 (and not the other pages) do not have the page number inside the span tags. The other page breaks do.

I assume this is just a mistake, rather than a test of how e-readers handle page breaks with optional elements present and absent.

How compile an Epub project and test.

Hi

I very new to Epubs, I used the following command for the tress example (I use ubuntu):

pandoc -f html -t epub3 -o output.epub c1.xhtml c2.xhtml package.opf titlepage.xhtml style.css script/*

and then I tried to view the epub in the chrome readium app, and the javascript appears as text.

Am I supposed to do this differently? I can't find any explanation of how these project files should be compiled. Your help would be most welcome.

Attribution within an XHTML content document?

According to the README.md, "As a contributor, you are able to specify attribution metadata only in the sample's package file." Does this mean that an XHTML or SVG content document cannot describe the owner, copyright, CC by SA, mail address, etc?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.