(which it did for back compatibility for 16 years),

undefined behavior, thanks to a report by Kirill Müller in

from the Unicode Basic Multilingual Plane, no longer corrupting

multi-byte-coded characters representable in the current native

encoding (at least on Windows 10 they were sometimes omitted,

issues with UTF-8 data when running in a DBCS

now accepts enhanced/arrow keys also with

user documents directory whose path is not representable in the

also on Windows when connection failure is signalled.

Problems with UTF-16 surrogate pairs have been fixed in

Older news can be found in text format in files

versions 3.x and from 2.10.0 to 2.15.3 are available at