HUGO

Chance of changing the Exif module?

The Exif implementation currently used by Hugo seems to be in a (very) dormant state - there have been no updates at all. On the other hand, there’s an Exif implementation for Go (GitHub - dsoprea/go-exif: A very complete, highly tested, standards-driven (but customizable) EXIF reader/writer lovingly written in Go.) that is actively developed and also permits to get at the IPTC data in JPEG files (according to the documentation).
One problem with the current implementation is that it incorrectly decodes the GPSAreaInformation tag by prepending the encoding (“ASCII”, for example). Also, XPKeywords are not correctly decoded (they are encoded in UCS-2, of all things).
I’m not sure if GitHub - dsoprea/go-exif: A very complete, highly tested, standards-driven (but customizable) EXIF reader/writer lovingly written in Go. does all this correctly, but there’s at least someone actively working on it. And one would have a chance to get at IPTC data, which are a lot more useful then Exif in many cases (e.g. keywords, descriptions etc.). For example, using IPTC data one could build galleries in hugo depending on the keywords in the images.

1 Like

I would welcome this update. I added the existing EXIF integration, and when I did, I think the current option was the best available.

I had a quick look at the library you link to, and it looks very good.

Could you create a GitHub issue to track this?

Done: Replace underlying Exif library · Issue #8586 · gohugoio/hugo · GitHub