https://bugs.documentfoundation.org/show_bug.cgi?id=150327

Buovjaga <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |ilmari.lauhakangas@libreoff
                   |                            |ice.org
         Whiteboard| QA:needsComment            |
           Severity|normal                      |enhancement
             Blocks|                            |109323
                 OS|Windows (All)               |All
     Ever confirmed|0                           |1
            Summary|.JPG files exported from    |Allow exporting of
                   |Draw and Presentation won't |non-progressive JPEG images
                   |play on Epson projector     |

--- Comment #1 from Buovjaga <[email protected]> ---
Doing a quick search I found this for a random model:
https://files.support.epson.com/htmldocs/bl1410/bl1410ug/Source/PCFree/Reference/pcfree_filetype_list_multi_table.html

For .jpg it has this laundry list:

Make sure the file is not:

CMYK format
Progressive format
Highly compressed
Above 8192 × 8192 resolution
Over 12MB in size
Named with a .jpeg extension

Then I found this topic:
https://ask.libreoffice.org/t/i-need-a-non-progressive-jpeg/32584

So it seems the problem is that we output progressive JPEGs without any option
to choose non-progressive.

It seems like an uncontroversial feature request, so I'll set to NEW right
away.

To losslessly convert from progressive to baseline, you could use jpegtran as
discussed here:
https://legacy.imagemagick.org/discourse-server/viewtopic.php?t=22141

jpegtran in.jpg > out.jpg

You can get jpegtran from https://jpegclub.org/


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=109323
[Bug 109323] [META] Graphic export bugs and enhancements (jpg, png, eps, tiff,
gif ...)
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to