Bug #836 possibly reintroduced: writeMetadata() destroys resource fork on MacOS X for big files (>1MB)
The fix for #906 (as I understand it) solves the problem by disabling the xattr handling for all Mac platforms. However, the Mac platforms were the reason we introduced the xattr handling in the first place, as otherwise the resource fork of images bigger than 1MB would be destroyed.
So I think that disabling this mechanism for all MacOS platforms is going too far. If we really want to do that, we should provide an alternative mechanism that preserves resource forks.
Updated by Robin Mills about 5 years ago
- Target version changed from 0.26 to 0.28
I've put in around 1200 hours of effort to get to code complete v0.26 and closed almost 200 issues. Regrettably, there are only 5 or 6 issues on which I have not been able to work. This is one. Deferred for v0.27.