ESC meeting agenda: 2022-02-10 16:00 Berlin time

[Mike Kaganski]

On 09.02.2022 18:45, Miklos Vajna wrote:
> Extra items are appreciated either in this document or as a reply to this mail:

https://bugs.documentfoundation.org/show_bug.cgi?id=147248 - in 
connection with WebP support 
(https://bugs.documentfoundation.org/show_bug.cgi?id=114532)

The problem raised in the tdf#114532 was that the implemented 
unconditional conversion of WebP into PNG was unwanted by some who 
wanted to use WebP in their documents (taking full advantage from the 
newly supported format), or who wanted to have the original along with 
the fallback for later time when the fallback could be dropped.

That brought some concerns, because introducing fallback along with 
original could later result in sudden "breakage" of existing images in 
the document after an upgrade that decides to drop the fallback (see 
comment 27). Later it was suggested that we could drop existing fallback 
from SVG already today, at which stage I filed the tdf#147248.

So there are some decisions that ESC could advise for *general* handling 
of fallback saved along with original media - just because adding such 
things is much easier than dropping it later. E.g., is it really 
possible to drop SVG fallback now? What should be pre-requisite for such 
drop, breaking backward compatibility of documents? What should be 
pre-requisite to *add* fallback to a format? Is it OK to drop original 
when there's no data loss (there's an obvious data loss when converting 
vector SVG to PNG, but possibly it's not that clear with bitmap WebP to 
PNG).

-- 
Best regards,
Mike Kaganski