Readium.org Frequently-Asked Questions (FAQ)

Below are FAQs divided into categories (Readium Foundation, Readium.js, Readium Chrome Extension, Readium SDK, and Readium LCP).

FAQs about the Readium Foundation (Readium.org)

What is the relationship between Readium Foundation and IDPF

Readium began as a project of IDPF, and IDPF helped instigate the Readium Foundation. But Readium Foundation is a completely independent non-profit corporation, governed by its members. Readium Foundation is focusing specifically on open source implementation, complementary to IDPF's mission as a trade and standards organization. IDPF is a member of Readium Foundation and is currently providing some administrative support for the Foundation as part of its contributions (and IDPF Executive Director Bill McCoy is acting the interim President of the Readium Foundation).

Will Readium.org support vendor extensions to EPUB?

Readium.org's initial focus is on acceleration full adoption of complete and consistent implementations of the EPUB 3 standard. Support for extensions that are not officially part of EPUB will therefore be discouraged in Readium.org projects. However, as a commercial-focused open source community, extensions that are widely supported may be adopted. For example, Readium Chrome Extension already supports the Apple extension for specifying fixed-layout EPUB metadata (META-INF/com.apple.ibooks.display-options.xml, etc.). 

FAQs about the Readium.js Project

What is the status of cross-browser support in Readium.js?

Readium.js is architected to work on any modern (HTML5) browser. However as of September 2013 Readium.js has been primarily developed using WebKit-based browsers (Chrome, Safari), and only lightly tested on Firefox and IE9/10.

FAQs about the Readium Chrome Extension

Is the Readium Chrome Extension Beta a consumer-grade EPUB reading system?

No, at this time the Readium Chrome extension is expected to be used primarily by authors, publishers, and developers creating and testing EPUB 3 content and tools. However RCE has over 100,000 users (as of September, 2013) and has been translated into 7 languages with the help of contributors, so this configuration seems to have utility for some end users and the Readium Foundation hopes to maintain it into the future.

Will Readium Chrome Extension open DRM-protected eBooks?

At this time there are no plans for Readium Chrome Extension to support DRM-protected eBooks.

Will Readium Chrome Extension support other publication formats besides EPUB?

Not any time soon.

Will the Readium Chrome Extension be accessible?

Yes! Initial accessibility support is implemented in version 0.9 and further support is anticipated in the future based on pending contributions from members.

Will the Readium Chrome Extension be localized to languages besides English?

Yes, 7 languages are available. Contributions of translation assistance will be very welcome, as an internationalization infrastructure is in place.

Does Readium Chrome Extension share code with Readium.js and Readium SDK?

Not yet. Readium.js and the core JavaScript modules Readium.js shares with Readium SDK were developed subsequent to the initial development of Readium Chrome Extension, which is not (as of September 2013) "synched up" with the new more modular architecture for these components. At some point in the future it is anticipated that Readium Chrome Extension will be refactored to utilize Readium.js components (and likely become a new-style Chrome App in the process).