[erlang-questions] v17 unicode support

[Vlad Dumitrescu]

Hi!

I'm not sure if I misunderstood something or if there is a problem in
17.0-rc1, but starting a shell normally gives

Erlang/OTP 17 [RELEASE CANDIDATE 1] [erts-6.0] [smp:4:4] [async-threads:10]
Eshell V6.0  (abort with ^G)
1> "Ȇ".
[518]
2> erl_scan:string("\"Ȇ\"").
{ok,[{string,1,[518]}],1}
3> lists:keyfind(encoding, 1, io:getopts()).
{encoding,unicode}
4>  $Ȇ.
518

while starting with "+pc unicode" gives the expected (for me) result.

Erlang/OTP 17 [RELEASE CANDIDATE 1] [erts-6.0] [smp:4:4] [async-threads:10]
Eshell V6.0  (abort with ^G)
1>  "Ȇ".
"Ȇ"
2> erl_scan:string("\"Ȇ\"").
{ok,[{string,1,"Ȇ"}],1}
3>
3> lists:keyfind(encoding, 1, io:getopts()).
{encoding,unicode}
4> $Ȇ.
518

Isn't 17.0 supposed to have the unicode support as default even in this
context?

regards,
Vlad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140221/e3790ba3/attachment.htm>