@geeboo/epub NPM

geeboo/epub.js

本epubjs是定制版，添加了在jszip解析的时候进行解密。

update

v1.0.10 1. 过滤文件 v1.0.6 1. 去除多余的console v1.0.5 1. 处理css 解密，将ciff 挂载到全局，方便解密 v1.0.4 1. 请求地址调整，部分地址会显示 /OEBPS/OEBPS/**.html 错误地址，目前自己处理成单层关键字file1

文件说明

-src
|-book 解析的入口
|-cliff 解析 cliff文件
|-archive jszip 文件读取模块
|-container 解析container.xml文件
|-section  生成内容请求队列
|-spine 生成地址队列
|-packaging packaging（路由）解析 `linear no` 表示不显示

解析钩子

 var book = ePub({
  // 解析书本时的前置构造，files 为文件列表包含所以的文件，bookObject为 book.js 实例 ，cb 为解释回掉要求使用return 返回
  openBefore: function (files, bookObject, cb) {
    // 如果你想在书之前访问一个文件可以  return Promise 
    // 如 return bookObj.load("META-INF/cliff-support.xml", type)   type :u8 、blob、text
    return cb()
  },
  // 返回一个异步方法，并且必须return 明文内容 return Promise 并在方法内容return 内容了
  contentBefore: function (entry, cb2) {
    console.log("2")
    // 为文件内容解析 entry 为jsZip 对象 entry cb2为默认请求
    // 如 return return entry.async("string").then(function (text) {
        //   return text;
        // });
    return cb2()
  }
});

.epub 文件解析流程

获得.epub地址 -> book.open(打开图书,"binary") -> book.openEpub() 初始化epub -> book.openCliff() 获得书籍信息「新增」-> book.openContainer() 获得内容路径地址,并返回 -> book.openPackaging() 格式化包的xml-> book.unpack() 拆解包的内容

以上openCliff、openContainer、openPackaging都是基于book.load对包的内容进行提取而后分享，而book.load是基于archive 提供的jszip的能力。

About

FuturePress Views

Epub.js is a JavaScript library for rendering ePub documents in the browser, across many devices.

Epub.js provides an interface for common ebook functions (such as rendering, persistence and pagination) without the need to develop a dedicated application or plugin. Importantly, it has an incredibly permissive Free BSD license.

Try it while reading Moby Dick

Why EPUB

The EPUB standard is a widely used and easily convertible format. Many books are currently in this format, and it is convertible to many other formats (such as PDF, Mobi and iBooks).

An unzipped EPUB3 is a collection of HTML5 files, CSS, images and other media – just like any other website. However, it enforces a schema of book components, which allows us to render a book and its parts based on a controlled vocabulary.

More specifically, the EPUB schema standardizes the table of contents, provides a manifest that enables the caching of the entire book, and separates the storage of the content from how it’s displayed.

Getting Started

Get the minified code from the build folder:

<script src="../dist/epub.min.js"></script>

If using archived .epub files include JSZip:

<script src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.1.5/jszip.min.js"></script>

Set up a element to render to:

<div id="area"></div>

Create the new ePub, and then render it to that element:

<script>
  var book = ePub("url/to/book/package.opf");
  var rendition = book.renderTo("area", {width: 600, height: 400});
  var displayed = rendition.display();
</script>

Render Methods

Default

book.renderTo("area", { method: "default", width: "100%", height: "100%" });

View example

The default manager only displays a single section at a time.

Continuous

book.renderTo("area", { method: "continuous", width: "100%", height: "100%" });

View example

The continuous manager will display as many sections as need to fill the screen, and preload the next section offscreen. This enables seamless swiping / scrolling between pages on mobile and desktop, but is less performant than the default method.

Flow Overrides

Auto (Default)

book.renderTo("area", { flow: "auto", width: "900", height: "600" });

Flow will be based on the settings in the OPF, defaults to paginated.

Paginated

book.renderTo("area", { flow: "paginated", width: "900", height: "600" });

View example

Scrolled: book.renderTo("area", { flow: "scrolled-doc" });

View example

Scripted Content

Scripted content, JavasScript the ePub HTML content, is disabled by default due to the potential for executing malicious content.

This is done by sandboxing the iframe the content is rendered into, though it is still recommended to sanitize the ePub content server-side as well.

If a trusted ePub contains interactivity, it can be enabled by passing allowScriptedContent: true to the Rendition settings.

<script>
  var rendition = book.renderTo("area", {
    width: 600,
    height: 400,
    allowScriptedContent: true
  });
</script>

This will allow the sandboxed content to run scripts, but currently makes the sandbox insecure.

Documentation

API documentation is available at epubjs.org/documentation/0.3/

A Markdown version is included in the repo at documentation/API.md

Running Locally

install node.js

Then install the project dependences with npm

npm install

You can run the reader locally with the command

npm start

Examples

View All Examples

Testing

Test can be run by Karma from NPM

npm test

Building for Distribution

Builds are concatenated and minified using webpack and babel

To generate a new build run

npm run prepare

or to continuously build run

npm run watch

Hooks

Similar to a plugins, Epub.js implements events that can be "hooked" into. Thus you can interact with and manipulate the contents of the book.

Examples of this functionality is loading videos from YouTube links before displaying a chapter's contents or implementing annotation.

Hooks require an event to register to and a can return a promise to block until they are finished.

Example hook:

rendition.hooks.content.register(function(contents, view) {

    var elements = contents.document.querySelectorAll('[video]');
    var items = Array.prototype.slice.call(elements);

    items.forEach(function(item){
      // do something with the video item
    });

})

The parts of the rendering process that can be hooked into are below.

book.spine.hooks.serialize // Section is being converted to text
book.spine.hooks.content // Section has been loaded and parsed
rendition.hooks.render // Section is rendered to the screen
rendition.hooks.content // Section contents have been loaded
rendition.hooks.unloaded // Section contents are being unloaded