You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use ZipFoundation to create archives of some old Mac files which include Resource Forks - this is so the files become safe to transport over third-party sync tools onto other file systems.
I'm using the FileManager zipItem function and, whilst archives are created, they are much smaller than the same file zipped using the Finder. Unzipping the produced archive also creates a zero byte output.
Is there a way to make ZipFoundation aware of Resource Forks, or is this unsupported at present?
Thanks.
The text was updated successfully, but these errors were encountered:
I was coming to ask about custom file icon support, but I think this issue covers it, right? I believe the custom file icons are stored in the resource fork. If so, adding support for the resource fork would resolve my issue with custom file icons. Should I create a new Issue for my particular use case?
Hello:
I'm trying to use ZipFoundation to create archives of some old Mac files which include Resource Forks - this is so the files become safe to transport over third-party sync tools onto other file systems.
I'm using the FileManager zipItem function and, whilst archives are created, they are much smaller than the same file zipped using the Finder. Unzipping the produced archive also creates a zero byte output.
Is there a way to make ZipFoundation aware of Resource Forks, or is this unsupported at present?
Thanks.
The text was updated successfully, but these errors were encountered: