https://bugs.documentfoundation.org/show_bug.cgi?id=114531
Julien Nabet <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Julien Nabet <[email protected]> --- (In reply to Tomaz Vajngerl from comment #3) > Well we need Jpeg-XR for full support of images in OOXML documents.. even if > it is just a "meh" format it is something MSO uses in some cases. So I > wouldn't close this one... Reading external/libjpeg-turbo/README, we use libjpeg-turbo-2.1.5.1.tar.gz for jpeg import support (but it seems also for export too considering we use functions like "jpeg_create_compress"). I don't know if libjpeg-turbo supports jpeg-xr if not, it means we must find a lib (compatible with LO license) which supports the format, in C or C++, well maintained, etc. Considering the size of OOXML specs (see https://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML#Criticism), I'm not sure it's a pb to not implement a standard which isn't even implemented natively by Gimp and Photoshop (see https://en.wikipedia.org/wiki/JPEG_XR#Software_support). Then we can wonder if we're talking about read support only or read and write support but quite quickly, if there's read-only support, people will complain they can't modify the images of a doc. Of course, we may convert the image in another format but 1) it adds even more complexity 2) it'll bother some users Finally I completely agree with https://bugs.documentfoundation.org/show_bug.cgi?id=114533#c5 : "Also removing support for a image format is much harder so adapting a new image format should take a lot of consideration as it can have long lasting effects" Perhaps it could be interesting to ask ESC opinion? -- You are receiving this mail because: You are the assignee for the bug.
