-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Unexpected Chinese Strings in Logs #2381
Comments
I can't reproduce any issues with the logging 🤷♂️ |
It's scrambled characters, not Chinese. |
This looks like ASCII being interpreted as UTF-16. You can tell by the 0A0D character. And no, the text doesn't mean anything, online translators will readily invent meaning for any random sequence of Chinese characters. |
I understand that this is not related to the Chinese language. Nevertheless, further investigation might be necessary. I will keep this issue open for six months to allow for additional feedback or reports from other users who may be experiencing similar problems. |
suspicious-strings-translated.txt Here is your suspicious-strings.txt "translated" from UTF-16 to UTF-8. Looks like normal logging, just with different encoding. |
Thanks for the help.
The log files are UTF-8 and either transferring the file to a different system or using a editor without UTF8 support would be the issue known as Mojibake: |
Brief description of your issue
I found unexpected Chinese strings appearing in the logs of System Informer. When translated, they seem to have real meaning rather than being the result of a character encoding issue.
The full string is here: suspicious-strings.txt
Steps to reproduce (optional)
Expected behavior (optional)
The logs shouldn't display unintended strings
Actual behavior (optional)
The logs include Chinese strings that appear to have a coherent meaning when translated (seems to be sexual in meaning though). These strings are unexpected and unrelated to my actions in the application.
Environment (optional)
The text was updated successfully, but these errors were encountered: