W3C home > Mailing lists > Public > public-publ-wg@w3.org > December 2018

Re: [AudioTF] Agenda 2018-12-14

From: Laurent Le Meur <laurent.lemeur@edrlab.org>
Date: Tue, 11 Dec 2018 13:13:14 +0100
Message-Id: <3BA59CED-CB0A-4C94-805B-F6CFA631DAA9@edrlab.org>
Cc: W3C Publishing Working Group <public-publ-wg@w3.org>
To: Matt Garrish <matt.garrish@gmail.com>
This is the main issue to open and discuss. 

Reading apps use common zip libraries for their system, and look for the mimetype file wherever it is. Up to developers who developed differently to raise their hand. 

Logically, this mimetype-first constraint has been crafted for streaming usage of EPUB (where the reader opens the zip file and get sequential chunks out of it). It doubt this is a standard way of handling EPUB files.


> Le 11 déc. 2018 à 12:39, Matt Garrish <matt.garrish@gmail.com> a écrit :
> The one “feature” of OCF that everyone seems to hate is that it requires the mimetype file be the first in the ZIP container. That makes packaging an EPUB more complicated than just zipping up all the files, since the mimetype typically won’t get inserted first in general zipping scenarios.
> If we remove this restriction from OCF 3.2, then we possibly break the loading of publications in reading systems that won’t process a publication without first encountering the mimetype. I have no idea how many that is, or if it’s common to fall back to finding a mimetype elsewhere in the zip if it’s not first.
> Matt

Received on Tuesday, 11 December 2018 12:13:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:33 UTC