Closed GoogleCodeExporter closed 9 years ago
No, the behavior should be to throw an error. This is a bug, and should be
fixed -
the encoding should be set to UTF-16 as you suggest when you change the key.
Original comment by joe.wreschnig@gmail.com
on 18 Jan 2010 at 12:25
This issue was closed by revision r80.
Original comment by joe.wreschnig@gmail.com
on 5 Feb 2010 at 5:23
Original issue reported on code.google.com by
cy...@home.se
on 18 Jan 2010 at 10:10