Description
The file RimWorld1-1-2552Mac.zip from my direct download link for macOS can't be extracted due to errors.
I tried different browsers but the file is always the same, its shasum is:
497a77f46ac146f7a6e5a87eb491dc5c067f3712 ./Downloads/RimWorld1-1-2552Mac.zip
When I unzip the file using a terminal, I see that there are problems unpacking language files:
error: cannot create RimWorld1-1-2552Mac/RimWorldMac.app/Data/Core/Languages/French (Fran�ais).tar
Illegal byte sequence
inflating: RimWorld1-1-2552Mac/RimWorldMac.app/Data/Core/Languages/German (Deutsch).tar
error: cannot create RimWorld1-1-2552Mac/RimWorldMac.app/Data/Core/Languages/Greek (+�+++++�+�+�+�+�).tar
Illegal byte sequence
...
My System
macOS 10.15.3 (19D76)
system language set to english
Hi,
the mac archive can be extracted without problems at my side, but i use windows not a mac.
Mosttimes when people got trouble to unarchive some files it is because they use an old tool.
And you don't need to unarchive these language pack's Rimworld will do that automatical if you change the language.
Just try it out if you still get an error when you change the language inside Rimworld.
Quote from: Canute on February 25, 2020, 08:31:50 AM
Mosttimes when people got trouble to unarchive some files it is because they use an old tool.
I am using the latest macOS and its standard unarchive / unzip utilities.
Quote
And you don't need to unarchive these language pack's Rimworld will do that automatical if you change the language.
Just try it out if you still get an error when you change the language inside Rimworld.
I didn't unarchive the language packs, just unzipped the Rimworld download zip file. I couldn't even start the app.
Nevertheless, thanks for your tips.
It looks like the encoding of the filenames caused some problems.
But I now could get it to unpack properly using a Windows VM.
We're looking at how to fix this going forward. Thanks for reporting.
Fixed, thanks for reporting (will be available once hotfix is released).
You should be able to re-download the fixed version now.
It'd be great if you could post back here to tell us the result and confirm it's fixed/not fixed.
Thanks greatly.