-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extraction error due to string culture differences #903
Comments
https://github.com/wabbajack-tools/wabbajack/blob/master/Wabbajack.VirtualFileSystem/Context.cs#L221 |
I have the Same Problem how do i fix it? when i rename the file it just downloads it wrong again i just cant figure out how to do this |
See here: |
Whoops. Wrong button. Still low priority. |
Marked as stale due to inactivity |
Closed due to inactivity |
This is still a bug. Why close issues due to inactivity? Just leave them labeled as stale. |
Want activity to keep bugs open? Have a datapoint: Wabbajack version: v3.7.1.1 Error: |
Describe the bug
During install of a list, the installer may fail due to a mod similar to Rayek's End having a degree symbol in one of its filenames. When extracting, the expected filename isn't as expected due to Windows interpreting the symbol natively in another language.
Within Rayek's End - SSE Expanded Edition 1.7-8285-1-7.zip as an example, there is the archived file "Meshes\Oaristys\Clutter\Mirror°.nif" which is expected by WJ... but when a Windows10 install with Japanese base (note: ENGLISH is used as main, but Windows may still interpret symbols differently) it reads the file as "Meshes\Oaristys\Clutter\Mirror・nif" which does not match. Thus, the installation fails.
Additional context
OS (Win 10 Japan running English as main) and Game type (SSE)
Logs
Wabbajack 2020-06-01 16_48_16.log
Above is reinstall attempt, below is after manually extracting and renaming the file in question to the expected "Meshes\Oaristys\Clutter\Mirror°.nif" within the mod directory in profile.
Wabbajack 2020-06-01 16_56_44.log
The text was updated successfully, but these errors were encountered: