Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relax "mimetype" requirements in OCF? #2

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 4 comments
Closed

Relax "mimetype" requirements in OCF? #2

GoogleCodeExporter opened this issue Mar 24, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

This is a very quick attempt to summarize a long on-list discussion ("Re: 
Authoring pain & requirements").  While providing a good signature that can be 
verified without understanding Zip or XML (container.xml), the "must be first, 
must be unadorned, must be uncompressed" restrictions make EPUB harder to 
create that may be needed.  Suggestion (some mutually exclusive):

-- Make "mimetype" optional
-- Allow trailing whitespace (e.g. "\r", "\n") on "application/epub+zip" in 
mimetype file content.
-- Allow "mimetype" to be anywhere and adorned and compressed

I (Garth) can't say I love this relaxation... but, the issue is logged for 
future discussion/decision.


Original issue reported on code.google.com by [email protected] on 19 Aug 2010 at 12:53

This was referenced Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant