-
Notifications
You must be signed in to change notification settings - Fork 27
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
[Bug|Minor][2.2.16] Some encoding issues with importing localized strings #107
Comments
Hi, could you zip up and attach your preset for this mod? you should find them under Foreman's It'll be 3 files with the same name, ending in The JSON file you screenshotted hopefully has the correct data and just needs to be parsed with the correct charset. I can figure it out once I have a copy. |
pY presets are huge and won't fit as an attachment as a whole, so I've uploaded the .pjson only (which by itself is a 16MB already xD): If import itself can't be fixed due to |
OK, I see. I'd like to try out a few encodings for Foreman to interpret stdout as, starting with UTF8 - are you able to compile Foreman yourself? If so, add If not, let me know and I can supply a binary. I have just tested this myself by manually injecting |
Sure thing, working on a PR in regards to graphs myself atm. |
Knowing which code you need to change is 99% of the problem :) Glad it worked, I'll get a PR submitted. |
While playing around with pY, noticed some translations are imported w/ wrong encoding
First, I thought of some UI issue, but the preset file shows same string:
Localisation in pY itself is correct:
The text was updated successfully, but these errors were encountered: