Your file was encoding in UTF-8, and you command has already successfully loaded the file into q workspace.
The reason you are not seeing the proper characters on screen is due to the encoding of your console, which defaults to GB18030 on Chinese versions of Windows. You can run this command to switch your console encoding to UTF-8 as well:
\chcp 65000
However, please note that Windows’ implementation of UTF-8 is somewhat buggy. So do expect to see some partly corrupted displays when you are showing information on a UTF-8 console sometimes. One possible work-around is to use an IDE instead, or work through the web interface of kdb+.
Thank you so much for your reply. I can use the web interface and the method really helps me out.
? 2017?9?23??? UTC+8??8:48:21?Flying???
Tongwei,
Your file was encoding in UTF-8, and you command has already successfully loaded the file into q workspace.
The reason you are not seeing the proper characters on screen is due to the encoding of your console, which defaults to GB18030 on Chinese versions of Windows. You can run this command to switch your console encoding to UTF-8 as well:
\chcp 65000
However, please note that Windows’ implementation of UTF-8 is somewhat buggy. So do expect to see some partly corrupted displays when you are showing information on a UTF-8 console sometimes. One possible work-around is to use an IDE instead, or work through the web interface of kdb+.