What Program Reads Epub

[Brook Mithani]

Ifyou are asking whether the MyCloud apps can read epub files, then you will probably need to add an epub reader app to whatever device you are using to run the MyCloud App, and then open the accessed file with the epub reader.

I would suggest you take some time, if you have not done so already to read through the My Cloud User Manual ( =439&type=25) to gain an understanding what the My Cloud is. What it is capable of. And how to configure/use the various options/features of the My Cloud.

I'm creating ebooks for a client using InDesign CC and she reports that the most recent EPUB I've created for her won't open in iBooks. As I don't own a smartphone or tablet I can't error-test on my end, but if you can think of anything that would lead to this error please let me know! I can't think of anything I've done differently in creating the EPUB, so maybe it's an issue with a recent CC or iBooks update? Has anyone else had this problem recently? The other ebooks I've made for her open fine.

Her report on what happened: "when I go to my downloads folder and double click the file -- it opens the book shelf in ibooks and shows that the file is there but it has no cover. When i double click the book the program doesnt do anything. it doesnt open."

Not sure which version, but I know she's on a Mac OS and NOT an iPad. I'm going to try to replicate the error on my end with a few Apple devices that my friends own, but haven't had the chance to do so yet. Do you have any clue at all what might be happening? Right now I'm sitting on my hands because I don't know where to begin!

Have you tried running an EPUB checker on your file to make sure it isn't actually anything on your end? Other than that I would just suggest making sure she has the most up to date version of iBooks.

So I tried running the ebook through two ebook checkers and also opened it up just fine on another iOS device (which *should* be the only thing you can use iBooks on--so why my client said she was running it on a Mac is a mystery to me). So far so nothing--there were a few errors about best use practices and inline objects that I'll tweak, but nothing catastrophic.

In your last post here, you also had the same problem with the cover, which I think was due to the CMYK mode settings. Now I have no idea if iBooks doesn't display cover images that are CMYK, but usually images should be RGB (or Grayscale) in EPUB in order for them to display in ADE and Nook.

Hi, I haven't had the time to really play around with this but if I'm remembering correctly the app speech central can read ePub files. Another possible solution could be learning Ally. They offer free accounts to students and it worked great for me. If you have any questions about that please feel free to email me at kproven...@gmail.com.

Indeed, Speech Central can. It can generate audio files, but it is also VoiceOver accessible, so the text is visible, in case you wish to know how to spell something in particular.

There is also an option to read continuously via the system voice. Highly recommended.

The Speech Center is really the best option for reading EPUB. I'm enjoying the program a lot and would recommend it highly. I hope only small improvements in some types of indexes with levels, to stay more organized navigation. But of all that I have tested, and I have done this a lot, I believe that this is the best.

I've just installed Vital Source Bookshelf and downloaded an epub file from Bookshare. It is reading correctly and the interface has a standard Mac layout. Here's the link;

-us/categories/200132467-Bookshelf-for-Mac-and-PC

EPUB is an e-book file format that uses the ".epub" file extension. The term is short for electronic publication and is sometimes stylized as ePub. EPUB is supported by many e-readers, and compatible software is available for most smartphones, tablets, and computers. EPUB is a technical standard published by the International Digital Publishing Forum (IDPF). It became an official standard of the IDPF in September 2007, superseding the older Open eBook (OEB) standard.[2]

The Book Industry Study Group endorses EPUB 3 as the format of choice for packaging content and has stated that the global book publishing industry should rally around a single standard.[3] Technically, a file in the EPUB format is a ZIP archive file consisting of XHTML files carrying the content, along with images and other supporting files. EPUB is the most widely supported vendor-independent XML-based e-book format; it is supported by almost all hardware readers and many software readers and mobile apps.[4]

The EPUB 3.0 specification became effective in October 2011, superseded by a minor maintenance update (3.0.1) in June 2014.[7] New major features include support for precise layout or specialized formatting (Fixed Layout Documents), such as for comic books,[8] and MathML support. The current version of EPUB is 3.2, effective May 8, 2019.[9] The (text of) format specification underwent reorganization[10] and clean-up; format supports remotely hosted resources and new font formats (WOFF 2.0 and SFNT)[11] and uses more pure HTML and CSS.[12]

EPUB 2.0 was approved in October 2007, with a maintenance update (2.0.1) intended to clarify and correct errata in the specifications being approved in September 2010.[6] EPUB version 2.0.1 consists of three specifications:

EPUB internally uses XHTML or DTBook (an XML standard provided by the DAISY Consortium) to represent the text and structure of the content document, and a subset of CSS to provide layout and formatting. XML is used to create the document manifest, table of contents, and EPUB metadata. Finally, the files are bundled in a zip file as a packaging format.

An EPUB file uses XHTML 1.1 (or DTBook) to construct the content of a book as of version 2.0.1. This is different from previous versions (OEBPS 1.2 and earlier), which used a subset of XHTML. There are, however, a few restrictions on certain elements. The mimetype for XHTML documents in EPUB is application/xhtml+xml.[15][a]

Styling and layout are performed using a subset of CSS 2.0, referred to as OPS Style Sheets. This specialized syntax requires that reading systems support only a portion of CSS properties and adds a few custom properties. Custom properties include oeb-page-head, oeb-page-foot, and oeb-column-number. Font-embedding can be accomplished using the @font-face property, as well as including the font file in the OPF's manifest (see below). The mimetype for CSS documents in EPUB is text/css.[15][b]

EPUB also requires that PNG, JPEG, GIF, and SVG images be supported using the mimetypes image/png, image/jpeg, image/gif, image/svg+xml. Other media types are allowed, but creators must include alternative renditions using supported types.[15] For a table of all required mimetypes, see Section 1.3.7 of the specification.

Unicode is required, and content producers must use either UTF-8 or UTF-16 encoding.[15] This is to support international and multilingual books. However, reading systems are not required to provide the fonts necessary to display every Unicode character, though they are required to display at least a placeholder for characters that cannot be displayed fully.[15]

The OPF specification's purpose is to "[define] the mechanism by which the various components of an OPS publication are tied together and provides additional structure and semantics to the electronic publication".[16] This is accomplished by two XML files with the extensions .opf and .ncx.

The OPF file, traditionally named content.opf, houses the EPUB book's metadata, file manifest, and linear reading order. This file has a root element package and four child elements: metadata, manifest, spine, and guide. Furthermore, the package node must have the unique-identifier attribute. The .opf file's mimetype is application/oebps-package+xml.[16]

The metadata element contains all the metadata information for a particular EPUB file. Three metadata tags are required (though many more are available): title, language, and identifier. title contains the title of the book, language contains the language of the book's contents in RFC 3066 format or its successors, such as the newer RFC 4646 and identifier contains a unique identifier for the book, such as its ISBN or a URL. The identifier's id attribute should equal the unique-identifier attribute from the package element.[16][c]

The manifest element lists all the files contained in the package. Each file is represented by an item element, and has the attributes id, href, media-type. All XHTML (content documents), stylesheets, images or other media, embedded fonts, and the NCX file should be listed here. Only the .opf file itself, the container.xml, and the mimetype files should not be included.[16]

The spine element lists all the XHTML content documents in their linear reading order. Also, any content document that can be reached through linking or the table of contents must be listed as well. The toc attribute of spine must contain the id of the NCX file listed in the manifest. Each itemref element's idref is set to the id of its respective content document.[16]

The guide element is an optional element for the purpose of identifying fundamental structural components of the book. Each reference element has the attributes type, title, href. Files referenced in href must be listed in the manifest, and are allowed to have an element identifier (e.g. #figures in the example).[16][d]

Of note here is that the values for the docTitle, docAuthor, and meta name="dtb:uid" elements should match their analogs in the OPF file. Also, the meta name="dtb:depth" element is set equal to the depth of the navMap element. navPoint elements can be nested to create a hierarchical table of contents. navLabel's content is the text that appears in the table of contents generated by reading systems that use the .ncx. navPoint's content element points to a content document listed in the manifest and can also include an element identifier (e.g. #section1).[16][18]

3a8082e126