Perhaps most surprising is that so many direct competitors are working together on a single project. The companies signing on include ACCESS, Aldiko, Bluefire Productions, Baker & Taylor, Benetech, Bokbasen, DAISY Consortium, Datalogics, De Marque, DILICOM,, Eden Livre (a joint venture of Gallimard, La Martinière and Flammarion), Editis, Evident Point, Feedbooks, Firebrand Technologies, Hachette Livre, IDPF, Izneo, Kobo, LIA (by Italian Publishers Association), Mantano, Numilog, Rakuten, Sony Corporation, TXTR, and Vibal Publishing House. Of perhaps more importance is the announcement of the new membership-based nonprofit Readium Foundation, encompassing a consortium of numerous international fixtures in the ebook and digital publishing market. We should do the same as in the other cases: No inline JavaScript at all.īut finding the way to change that policy would be easier.PARIS: Today at the Salon du Livre (the Paris Book Fair) launched its new EPUB3 SDK Project to develop a commercial grade open source rendering engine optimized for native apps on devices and to accelerate the adoption of EPUB3 and HTML5. Most of the interactive activities are not working.

Can we include that object in common.js using Python when exporting? If you can do that, I'll do the next point:

Please tell me if you find how to apply that.į229589 makes JavaScript work in many cases (Free Text iDevices, iDevice togglers, FX, definition lists and iDevices with feedback), but we have to improve that:Īs you'll see, $exe_i18n is defined in common.js instead of being in the HTML right before that file is included (see common.py - getJavaScriptStrings). I tried to allow inline JavaScript execution, but I couldn't. It refuses to execute inline JavaScript because it violates the Content Security Policy directive.

Readium google chrome