[vc_row content_placement=”middle” text_color=”#1d3e80″ type=”color” bg_color=”#f6f6f6″ padding_top=”” padding_bottom=””][vc_column width=”1\/3″ offset=”vc_col-xs-12″][vc_column_text css=”.vc_custom_1714431323005{padding-top: 10px !important;padding-bottom: 30px !important;}”]<\/p>\n
[\/vc_column_text][\/vc_column][vc_column width=”2\/3″ offset=”vc_col-xs-12″][vc_single_image image=”17719″ img_size=”full”][\/vc_column][\/vc_row][vc_row padding_bottom=””][vc_column][vc_column_text]<\/p>\n
[\/vc_column_text][\/vc_column][\/vc_row][vc_row padding_top=”” padding_bottom=””][vc_column width=”2\/3″][vc_column_text]EPUB\u00a0is an open file format<\/em> for electronic publications<\/i>. By publication, we usually mean book, but the scope is wider and includes long-form articles, digitized comics etc. For the sake of simplicity, we\u2019ll use the term ebook<\/em> in this documentation. By open file format, we mean that the specification is in free access on W3C website<\/a>, and that developers can freely create applications for generating or reading EPUB files (.epub), now and in the future.<\/p>\n EPUB is based on Web Standards: it defines a means of representing, packaging and encoding structured and semantically enhanced Web content \u2014 including HTML, CSS, SVG, images, and other resources \u2014 for distribution in a single-file format.<\/p>\n In practice, an EPUB file is a zip archive which contains XML structures, HTML and CSS resources, images and – with EPUB 3 – javascript code, audio and video assets.<\/p>\n Using open Web Standards in EPUB brings many advantages to the publishing industry:<\/p>\n In short, using Web Standards, the publishing industry avoids reinventing the wheel … note that it must still adapt this \u201cwheel\u201d to the chapters and pages of ebooks, i.e. the electronic version of a codex<\/i>.<\/p>\n EPUB is today the reference format for distribution and interchange in the digital publishing industry, as it allows publishers to produce and send a single digital publication file through multiple distribution workflows and offers consumers a great deal of interoperability between software\/hardware, for reflowable and fixed-layout ebooks.[\/vc_column_text] EPUB had its roots in the interchange format known as the Open EBook Publication Structure (OEBPS). OEBPS 1.0 was approved in 1999 by the Open eBook Forum, an organization that later became the International Digital Publishing Forum (IDPF). Subsequent revisions 1.1 and 1.2 were approved by the IDPF in 2001 and 2002 respectively.<\/p>\n It was realized that a need existed for a format standard that could be used for delivery as well as interchange, and work began in late 2005 on a single-file container format for OEBPS, which was approved by the IDPF as the OEBPS Container Format (OCF) in 2006. Work on a 2.0 revision of OEBPS began in parallel which was approved as the renamed EPUB 2.0 in October, 2007, consisting of three specifications: Open Packaging Format (OPF), Open Publication Structure (OPS) and the previously defined OCF.<\/p>\n EPUB 2.0.1<\/strong>, a maintenance update to the 2.0 specification intended to clarify and correct errata in the specifications, was approved in September, 2010.<\/p>\n EPUB 3.0<\/strong> superseded EPUB 2.0.1 in October, 2011, and in June 2014 appeared a maintenance release named EPUB 3.0.1 (often written 3.01). EPUB 2.0.1 was then considered obsolete and no longer maintained.<\/p>\n EPUB 3.1<\/strong>, was released in January 2017, just before the IDPF merged into the W3C. This version wasn’t 100% backward compatible with EPUB 3.0.1. and for this reason the publishing industry did not adopt this version.<\/p>\n EPUB 3.2<\/strong>, was released in May 2019 and is the result of the work of the W3C EPUB 3 Community Group. This version is 100% backward compatible with EPUB 3.0.1. and this is the current version of the specification.<\/p>\n EPUB 3.3<\/strong> is now almost ready. This work is done by members of the W3C EPUB 3 Working Group; mainly editorial work, but offers minor additions. This version is 100% backward compatible with EPUB 3.2, and this is the first version of EPUB 3 which will be an official W3C standard.[\/vc_column_text] Here\u2019s a list of what have been added and\/or improved in EPUB 3:<\/p>\n Things that have been removed:<\/p>\n [\/vc_column_text] The EPUB 2 format (2007) had no concept of fixed-layout; this notion appeared in EPUB 3.0.<\/p>\n You may open reflowable<\/i> or fixed-layout<\/i> EPUB files: what does this mean?<\/p>\n In a reflowable EPUB, the content is fluid and fits the size of the screen. If you read on a smartphone, you\u2019ll get perfectly readable characters on small pages. Novels are usually published as reflowable ebooks because their layout is simple. But the reflowable format is not always ideal, especially when it comes to designs where the layout is critical, i.e. for:<\/p>\n 1\/ creating sophisticated layouts (such as art books) A fixed-layout ebook defines a viewport, i.e. the size of the \u201cpage\u201d in pixels, and usually contains many images exactly positioned relative to text. Some good examples of fixed-layout publications are photo books, magazines and comics. An electronic \u201cpage\u201d is the strict rendition of a printed page : on a small screen, you\u2019ll usually have to zoom and scroll in the page (often vertically AND horizontally) to read the text.<\/p>\n [\/vc_column_text] When it come to EPUB 3 and especially fixed-layout EPUB 3, reading systems have different skills. It is now quite common for reading applications on mobiles, tablets or PCs to support EPUB 3 with fixed-layout: this is especially the case for those based on the Readium toolkit. But this is not the case for most applications based on the Adobe RMSDK, which includes an obsolete Readium codebase and is only good at processing EPUB 2.<\/p>\n Legacy e-readers (specialized devices with a black and white, touch-less screen, low memory, low computing power) are also only capable of processing EPUB 2. But several modern e-readers process EPUB 3 and correctly support sophisticated text-oriented layout, combined with images. The user experience is still constrained by the black and white 256 shades of grey of the device: good enough for textbooks, but not for comics or children books. Multimedia and interactivity are impossible due to the lack of power of such devices. Still, modern e-readers process simple EPUB 3 publications.<\/p>\n We’re still missing a clear indication of a full EPUB 3 support (including fixed-layout) on most bookseller platforms and common reading applications. Let’s hope that the multiplication of Readium based applications and the adoption of the LCP DRM<\/a> by e-distributors will soon solve this issue.<\/p>\n In order to show the path to EPUB 3 and LCP, EDRLab has released Thorium Reader<\/a> a free, accessible, multi-lingual and open-source desktop application.[\/vc_column_text] Latest<\/p>\n Stable<\/p>\n [\/vc_column_text][\/vc_column][vc_column width=”1\/3″][vc_wp_custommenu nav_menu=”9″][\/vc_column][\/vc_row][vc_row][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row padding_top=”” padding_bottom=””][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row padding_top=”30″ padding_bottom=”60″][vc_column width=”1\/2″][vc_single_image image=”17714″ img_size=”full” onclick=”custom_link” link=”https:\/\/www.edrlab.org\/readium\/”][vc_column_text font_size=”16″ line_height=”24″]<\/p>\n The Readium projects provide rock-solid, performant building blocks and applications for processing EPUB3 publications. EDRLab is participating to the Readium codebase maintenance and evolution.<\/p>\n\n
A brief history of the EPUB format<\/h2>\n
Features specific to EPUB 3<\/h2>\n
\n
\n
Reflowable vs fixed-layout EPUB 3<\/h2>\n
\n2\/ combining text and images (such as cookbooks)
\n3\/ mixing text with audio and video (such as textbooks)
\n4\/ creating interactive books, with embedded software to manage interactions.<\/p>\nEPUB 3 support in reading apps<\/h2>\n
Useful links<\/h2>\n
\n
\n
Other projects<\/h3>\n
Readium<\/h4>\n