At some point peekCString became locale aware. This is a double bug, since (a) decodeString was being applied to the result and (b) the locale might not be UTF-8, but the string being decoded always is.
The fix is to use peekCAString which bypasses the locale decode, then continuing to do UTF-8 decode.
Description
At some point
peekCStringbecame locale aware. This is a double bug, since (a)decodeStringwas being applied to the result and (b) the locale might not be UTF-8, but the string being decoded always is.The fix is to use
peekCAStringwhich bypasses the locale decode, then continuing to do UTF-8 decode.Checklist
[x] I've read CONTRIBUTING.md
[x] I've considered how to best test these changes (property, unit, manually, ...) and concluded: tested locally
[ ] I updated the
CHANGES.mdfile: N/A