[MGNLIMG-179] Add support for CMYK and "broken" JPEGs Created: 26/Nov/15 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | image operations |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Richard Unger | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
LFRZ |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
Please add support for CMYK images, as well as more general support for JPEG images which aren't 100% spec. conformant. Background: we have a large setup with >100GB of DAM data. Our editors use images a lot. Over the years, we have seen many instances of the following two problems: 1. CMYK JPEGs. 2. "Slightly broken" JPEGs To try to fix this, we have come across the following library: https://github.com/haraldk/TwelveMonkeys We are testing it in our QS, but it seems to work very well. Just add the library to the classpath (no other configuration is needed!) and magnolia can suddenly handle CMYK and most "buggy" JPEGs just fine. Please consider adding 12Monkeys to the standard release. |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |