Closed cleishm closed 6 years ago
It was incorrectly being encoded as 0x00, rather than 0x80. It was decoding correctly, as 0x00 and 0x80 are (somewhat) equivalent.
It was incorrectly being encoded as 0x00, rather than 0x80. It was decoding correctly, as 0x00 and 0x80 are (somewhat) equivalent.