I'm not talking about malicious fonts, but font stacks are complicated regardless of the encoding being fed in. You seem to think I'm blaming it on the font. I

I'm not talking about malicious fonts, but font stacks are complicated regardless of the encoding being fed in. You seem to think I'm blaming it on the font. I'm not. I'm blaming it on the font stack (CoreText) I avoided using the term "unicode" to refer to a bug in the font stack because font stack bugs don't always have to be specific to unicode. You keep saying "unicode parsing"; that's a meaningless term in this context. > Yet on your blog you allude to just that with the left/right comments, though, to be fair, you state that you really don't know the problem: That doesn't have to do with endianness or BOM, that's a totally different kind of ordering. It's ordering of the code points, not the code units. > This is claimed to be a dissection of the issue, but there is not even a stack trace present, and yet you joke about that... It's a dissection of the string. Not a full debugging of the issue.