I checked in last versions(stable and experimental) with int 65001 and it is using UTF-8 correct.
I cannot reprocedure the error.
Only by using and O instead of 0 than I can get it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
UTF-8 is in 65001 number.
This is a documentation problem.
Probably "ISO-8851-1" is also a typo,
which should be "ISO-8859-1" and
28591 in number.
I mean, "UTF-8 is 65001 in number."
I checked in last versions(stable and experimental) with int 65001 and it is using UTF-8 correct.
I cannot reprocedure the error.
Only by using and O instead of 0 than I can get it.
You misunderstood the bug. The bug is that you cannot write 'UTF-8' to the field. It only accepts numbers.
ved with ID 3010934 custom code as String or integer
Fixed by Matthias' patch #3010934.