Jon Sneyers

Not really. Is anyone interested in doing an independent implementation? Or to get the format formally standardized? It's basically a matter of converting the source code to precise plaintext, which...

Cool! I suggest we put the spec in https://github.com/FLIF-hub/FLIF-doc – it doesn't really make sense to put it in the repository of a specific implementation. https://github.com/panicbit/flif-rs/blob/master/spec.md is a good start;...

@nbraud for the Rust implementation you might want to collaborate with @panicbit. As for the spec itself: the work-in-progress document is here: https://github.com/FLIF-hub/FLIF-doc/tree/master/spec It's very incomplete at the moment, but...

The comparison in the link above is not quite fair, since it is mixing 4:2:0 chroma subsampled and non-chroma subsampled and calls both of them "lossless", while the former actually...

Not really. PNG and PPM only support 4:4:4.

You can compile with -DFLIF_USE_STB_IMAGE and then it should build without libpng, with a built-in png reader/writer. That's what is done in the Windows build by default, to avoid the...

Sounds like a good idea! First I want to get the stream format finalized though, so I'm putting this at Milestone M2.

Thanks for the ideas. I just committed https://github.com/FLIF-hub/FLIF/commit/9644035bb13e7861d9dc5d7a2fa294ca0de50156 which improves low-quality lossy encoding. - Gaussian filter: to some extent, we are already doing something like this. The effect of the...

@whocares0101 What is the purpose of transcoding via a lossless format? You can do something like `flif -e input.png - | flif -d - - | convert - output.png` (or...

So you can use `flif -e input.png -` and the output to stdout will be a FLIF file. And for the other direction you can use `flif -d input.flif -...