Closed el-lsan closed 9 years ago
Confirmed to exist only in Java version, the encoding is probably lost during toString or charAt returning to two bytes instead of one - also - I have motives to believe that the problem is with charAt as header should always be 22 bytes long, and it's failing in Java, having to use in most cases 21 and some rare cases 20
Sorry for taking so long to solve it, I completely forgot about it, solved in 9887cc5395d51bc5f664d11930ae34cad6d681e9
there's an issue with encoding for noneglish characters