https://bugs.documentfoundation.org/show_bug.cgi?id=114533
--- Comment #4 from Tomaz Vajngerl <qui...@gmail.com> ---
It is our responsibility to the user that the document he creates can be opened
with older versions of LO and other office suites. It is true that there is no
limitations which image formats should a document format support (neither by
ODF nor OOXML - just recommendations), we still need to choose the formats that
are widely used and supported by others. When a less supported format is used,
we need to warn the user that, which means we need to implement this missing
functionality.
Also there are other considerations in addition as every new library increases
the size of LO and increases the maintenance burden and things needed to be
tested. So by that we shouldn't adopt just any image format but one that would
be at least used a lot (yes and that generally is the chicken or the egg
problem why even we have more capable formats we still use many decade old
ones).
Generally I would avoid PackJPG or Lepton as they can save you some % by using
a modern entropy coder, but that is not that high to be worth it (it is much
less gain when using properly optimized JPEG files AFAIK). They are mostly used
by cloud storage providers (it was created by dropbox) where they can just
silently losslessly compress the images and gain space (even 5-10% for
petabytes of images is a lot). Support of both is practically non-existent.
I'm not too keen by adapting WebP now when the next-gen format based on AV1 is
not too far away (PIK, also developed by google is looking promising) and
Microsoft being part of AOM alliance I would expect to see support added to
Windows programs as well. WebP has support in Chrome, but generally, even on
Linux, it mostly isn't supported in image viewers.
FLIF is a great lossless image encoder, but currently it lacks support
practically everywhere. Not sure why we should adopt it when it is a good
chance it will be used just by a couple of people. It also uses a CABAC variant
for compression, which legal status is unknown. I would avoid - much more keen
to support WebP instead if I have to choose.
JPEG XR is the only format which I would be comfortable to add. The reason is
that it is supported and used by MSO in some situations (if you apply a image
filter, the original is stored in JPEG-XR so the user can revert the applied
filter) and it is generally supported on every Windows 7 and beyond. The
problem with JPEG XR is that it is not really much of an improvement over JPEG
or PNG (sometimes it is even worse) and that the open-source libjxr is
practically un-maintained library.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
