-
Notifications
You must be signed in to change notification settings - Fork 57
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
Don't support Chinese GBK encoding #127
Comments
Hello! Could you please clarify this? The extension itself is encoding-oblivious it deals with the JS strings decoded by the editor. So if VSCode supports GBK, then Rainbow CSV should "support" it too. Or are you talking about RBQL? |
Thank you for the demo! Did you try to manually switch the encoding to "GBK" by clicking on the encoding button at the bottom? what happens in that case? Does this still happen with other extensions disabled? |
I've tried it and it's very effective. |
Thanks! I did some tests with your file and in my case VSCode always opens it with UTF-8 encoding no matter if Rainbow CSV is enabled or not. But if I manually switch the encoding to GBK it fixes the characters and it works with Rainbow CSV too. So I don't think that Rainbow CSV is causing this issue, moreover extensions do not have capability to initiate encoding switch: microsoft/vscode#824. |
In my case, when I disable Rainbow CSV extension it becomes normal. Do you set the |
I turned off all the extensions except Rainbow CSV and the problem continued. The question seems to be |
Sorry for the late reply, I was able to reproduce the problem with |
Looks like this is actually related to an issue in the VSCode itself see microsoft/vscode#39084 and microsoft/vscode#127936. And actually, it is possible to reproduce the problem even with Rainbow CSV disabled - if you switch the file type of your file to e.g. 'C++' in the bottom right corner, not only file type would change but encoding too and garble the characters. |
Don't support Chinese GBK encoding. It always seems to use utf-8 encoding.
The text was updated successfully, but these errors were encountered: