Image Size
| Project: | EPUB Maintenance |
| Component: | General |
| Category: | bug report |
| Priority: | normal |
| Assigned: | GKerscher |
| Status: | dismissed |
Jump to:
Is a one byte image an error?
EPUB fails on large image files.
Description
Issue Id:
3
Resolution:
Proposed Resolution is dismissed.
This issue was submitted as a test and should simply be dismissed.
- Login to post comments
Comments
#4
I think we should generalize this: should there be minimal requirements for reading system conformance in the spec (e.g. Reading System must be able to process images below certain size). In real life there are going to be limits, the question is do they belong in the spec.
#5
I'm not sure I understand the question. A one byte image? Do jpeg, png or svg allow such a thing? I doubt it, but that's not part of our spec. If the image is a legal image in a core type, it is legal in OPS. What does "EPUB fails on large image files" mean? What is "EPUB"? How does it fail?
Also, the comments for this post seem to start with #4. Where are 1-3?
#6
I think what issue meant to say was "one megabyte" image.
#7
Ah. Well, that makes slightly more sense. Though I am still confused by the second half. As for 1 MB images - of course. But all Reading Systems have resource limitations, and particular images may be a problem. Though, 1 MB hardly seems huge by todays memory standards.
#8
This was a seeded post, i.e. just a sample from an overview discussion - any Maintenance Group member can edit the issue text itself to clarify the wording.
#9
I'm also confused by the issue. Downgrading image files for limited devices doesn't appear to be a spec issue -- it's a processing issue, and thus, falls outside of our mandate.
#10
I don't see any button enabling me to edit this issue. Perhaps it's set to only be editable by the issuer?
#11
Dismissed as it was simply used to test the wiki.