Page 1 of 1

FLIF lib 0.2 update

Posted: 2016-10-07T17:48:41-07:00
by Marsu42
IM doesn't seem to feature the latest FLIF format 0.2 - images generated by im cannot be read by the Windows Explorer plugin (based on the 0.2 lib), while images converted with flif's own command line encoder can. If so, please update - thanks.

https://github.com/FLIF-hub/FLIF/releases
https://github.com/fherzog2/flif_window ... n/releases

Re: FLIF lib 0.2 update

Posted: 2016-10-07T23:47:06-07:00
by dlemstra
We upgraded flif to 0.2. My guess is that it was no longer working because metadata was added.

Re: FLIF lib 0.2 update

Posted: 2016-10-08T02:43:13-07:00
by Marsu42
dlemstra wrote:We upgraded flif to 0.2. My guess is that it was no longer working because metadata was added.
Thanks - I guess the reason that it doesn't appear in the git log (http://git.imagemagick.org/repos/ImageMagick/activity) is that you just updated the .h and the .c (http://git.imagemagick.org/repos/ImageM ... ers/flif.c) remained unchanged? Just asking out of curiosity, I tried to compile im myself and was dazzled by t he complex delegate requirements.

I've suggested flif to Phil Harvey for incorporation into exiftool. If he works together with the flif author, that should result in a sane and stable metadata implementation: http://u88.n24.queensu.ca/exiftool/foru ... l#msg38902

Re: FLIF lib 0.2 update

Posted: 2016-10-09T02:21:54-07:00
by dlemstra
The API did not appear to be changed so I only updated our copy of flif (http://git.imagemagick.org/repos/flif/commits/master). What do you mean by complex delegate requirements?

Re: FLIF lib 0.2 update

Posted: 2016-10-09T11:18:59-07:00
by Marsu42
dlemstra wrote:What do you mean by complex delegate requirements?
My experience with compiling im was that it's not a matter of configure and make, but to get all file formats inside you have to hunt down and install a lot of libs. That's why I'm happy that there are complete and updated binary releases of im all the time - thanks!