-
Most modern shells will be UTF-8 encoded rather than ASCII.
kdb+ is storing the information correctly – it is just being displayed differently than you expect.
On my machine:
$ locale LANG=C.UTF-8 LANGUAGE= LC_CTYPE=”C.UTF-8″ LC_NUMERIC=”C.UTF-8″ LC_TIME=”C.UTF-8″ LC_COLLATE=”C.UTF-8″ LC_MONETARY=”C.UTF-8″ LC_MESSAGES=”C.UTF-8″ LC_PAPER=”C.UTF-8″ LC_NAME=”C.UTF-8″ LC_ADDRESS=”C.UTF-8″ LC_TELEPHONE=”C.UTF-8″ LC_MEASUREMENT=”C.UTF-8″ LC_IDENTIFICATION=”C.UTF-8″ LC_ALL=
UTF-8 encoding for �� 0xC3 0xB4
Testing this in kdb+
q)`char$0xC3B4
“ô”
q)`$`char$0xC3B4
`��i-code>
For your shell to print the extended ASCII table characters you will need to make some changes outside of kdb+.