-
Notifications
You must be signed in to change notification settings - Fork 218
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
Encodings #423
Encodings #423
Conversation
You beat me to it, but at least I got the time to clean up and properly set up my local repo :). I'll test it in a minute |
Fantastic, thank you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remind: The CN/credits.txt is using GB2312... not the UTF-8...😂
@Mishasama This is a change to make them show up correctly on Github. The encoding of the game files will remain. :) |
Is that file read by the game expecting that encoding? I assumed that's just an info file, so they're all exported as unicode, right now. This was the state before any encoding changes:
If for whatever odd reason the CN credits file needs to be in that particular codepage, just add a rule to the bottom of gitattributes (later rules take precedence, as per git docs). |
Updated README.md to reflect the changes fixed by TheIndieStone#423 and did some minor rewording/improvements
I know what is this... But I don't know how to add the rule for this file.😓 Maybe like this?
|
OK sooooo: the game reads the credits.txt to show it under the language selection (zombie.Lua.LuaManager.GlobalObject#getTranslatorCredits(Language)). It currently does not specify an encoding for doing that, so it defaults to the system encoding (WIN1252 in my case, German windows). That means: it doesn't really matter what we encode the file in: it will always be broken on one system or another, unless that is changed. |
Updated README with changes from #423 + fixes
Attempt to resolve #155