idpf / epub3-samples Goto Github PK

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.

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?

In your features matrix, the links to moby dick with overlays points to moby-dick.epub instead of moby-dick-mo.epub

I just noticed that the link to download the Linear Algebra title on the samples page (https://github.com/IDPF/epub3-samples#linear-algebra) appears to be pointing at the Kusamakura title by accident.

Dave

With epubcheck 4.0.0 which is claims to support "EPUB Region-Based Navigation 1.0" I get errors like:

Undefined property: 'panel'.
Undefined property: 'ballon'.

Anyone knows if this is an issue with the sample or with epubcheck 4.0?

How to handle the nav.xhtml if the size of the file is greater than 300 Kb

are these EPUB3 examples backward compatible with EPUB2 readers?

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?

I tried checking "expand CSS" when converting using calibre, but it didn't work

Thank you .

I want to test this when I using an epub reader open it ( for example ibook, it tell me it is drmed ).

http://idpf.github.io/epub3-samples/samples.html
The last link for Wasteland is https://drive.google.com/uc?export=download&id=0B9g8D2Y-6aPLZ0s0cjFaZHJOYms which is the same as the one immediately above (non-obfuscated WOFF)

i find indesign so hard to build creative reflowable epub . so is there any replacement ?

I'm looking for form/input example like...
http://www.idpf.org/accessibility/guidelines/content/script/forms.php
but can't find any.

Thanks.

Dear All,

I am getting warning message while using the Charis fonts. Can I remove these fonts from the ePub. This will have an impact in the quality of rendering of contents in readers?

Is there any vital reason for using these Charis fonts in the ePub?

Thanks,
Sudhakar

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.