Although we don't have enough tests about utf-8 position encoding, i.e.
it is not good to decide to use utf-8, it is completely wrong to not
passing a decided encoding back to client on initialization.
Edit: it doesn't work correctly under utf-8, so we currently always use
utf-16. We may fix it in v0.14
