Bug #910
Bug #836 possibly reintroduced: writeMetadata() destroys resource fork on MacOS X for big files (>1MB)
0%
Description
I believe that the fix for #906 reintroduced bug #836.
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.
Related issues
History
Updated by Robin Mills over 8 years ago
- Priority changed from High to Normal
- Target version changed from 0.24 to 0.25
I'll take a look at this on Saturday. I believe the earlier fix will be effective Lion (MacOS-X 10.7) and earlier. Might be able to sneak this into 0.24.
Robin
Updated by Robin Mills about 7 years ago
- Status changed from New to Assigned
I've changed the status to "Assigned" to help me remember to do something about this for v0.25.
Updated by Robin Mills over 6 years ago
- Target version changed from 0.25 to 0.26
Deferred to v0.26. Insufficient time to deal with this for v0.25.
Updated by Robin Mills about 5 years ago
- Target version changed from 0.26 to 0.28
Volker
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.