Display of Chinese characters #87
-
|
Hi smklimenko. Sorry for not replying your answer last time. I have tried the example on official website, and it works in kdb console.
However, the data I have is retrieved from mysql database using odbc interface. The columns that can not be properly displayed in the kdb console are
So I guess is the plugin does not support GBK encoding? I will attach the data file. Thanks a lot if you have time to take a look. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
ok, so, you have another encoding for your data. Unfortunately, there is no way do change encoding for the console as the data is processed and converted inside connection but what I can do - set encoding for a connection instead that you can defined in an instance configuration. Something like that: In this case all text data received from the instance will be converted using the encoding but if you have one encoding for one data and another for another table that won't work. Actually, it won't work in any case as there is no way to identify encoding looking at a random text data. Will the solution with a connection encoding work for you? |
Beta Was this translation helpful? Give feedback.
-
|
Sure! That would be great if you could add this functionality during the instance creation. Thanks for your instant reply again! |
Beta Was this translation helpful? Give feedback.
-
|
ok. it will take a day or two to be approved but jetBrains but if you wish, you can download and instance version 5.2.0 manually to try it: https://plugins.jetbrains.com/plugin/16746-kdbinsidebrains/versions/stable/461933 The option called codepage and as other options can be set in Settings, per Scope or per Instance, depends on what's better for your case. |
Beta Was this translation helpful? Give feedback.
ok, so, you have another encoding for your data. Unfortunately, there is no way do change encoding for the console as the data is processed and converted inside connection but what I can do - set encoding for a connection instead that you can defined in an instance configuration. Something like that:
In this case all text data received from the instance will be converted using the encoding but if you have one encoding for one data and another for another table that won't work. Actually, it won't work in any case as there is no way to identify encoding looking at a random text data.
Will the solution with a connection encoding work for you?