(03-03-2018, 08:51 AM)rich2005 Wrote: ...
In the meantime, you could use some alternative application such as XnViewMP
I do use XnViewMP, possibly thanks to you or maybe someone else on this forum. It is very nice/useful, however if it is capable of editing metadata I'm not aware of it. I do also use ExifTool which can be used to edit.
To be honest editing metadata is not something I see as important for GIMP to do but what is important is preservation of metadata. I can appreciate that this is a tough problem. Depending on changes that are made using GIMP some metadata becomes invalid and should probably either be altered accordingly or, at worst, omitted. It appears to me that GIMP has been solving this problem by omitting extensively.
Based on pretty limited experience GIMP 2.9.? appears better than 2.8.? but still NOT good.
(03-03-2018, 08:51 AM)rich2005 Wrote: ...
Will there be a 32 bit version for Windows? Possibly not, the trend is moving away from 32 bit, it has a decreasing user base and application maintainers are unwilling to spend time/resources on two packages.
...
I can appreciate the problem presented by trying to maintain both 32 & 64 bit versions especially if they are supposed to be functionally equivalent. I'm not expecting that but it is causing me to make my own migration to 64bit. Right now I have that for Windows, where my version 7 will become out of favor before long, but not Linux.
Something related to this which I've also noticed is that the image files saved by GIMP are not backward compatible. Would it NOT make sense to use a new file extension (i.e., different from .xcf) going forward (i.e., for GIMP 2.9.?+)? Developers need to expect that users will need to be able to use both versions for some amount of time going forward. The way it is now, I have to add an extension of my own to try and keep track of this but it would be better if the OS, at least, was able to pick a valid program when choosing what to launch. In that, associate files, based on extension, with a valid program.