This does not mean confusables.txt is wrong. It means confusables.txt is a visual-similarity claim that has never been empirically validated at scale. Many entries map characters to the same abstract target under NFKC decomposition (mathematical bold A to A, for instance), and the mapping is semantically correct even if the glyphs look nothing alike. But if you treat every confusables.txt entry as equally dangerous for UI security, you are generating massive false positive rates for 96.5% of the dataset.
这里有悠久的历史，璀璨的文明，孕育了各式各样的古文明以及世界三大宗教。
，推荐阅读新收录的资料获取更多信息
None of this is wrong. These guarantees matter in the browser where streams cross security boundaries, where cancellation semantics need to be airtight, where you do not control both ends of a pipe. But on the server, when you are piping React Server Components through three transforms at 1KB chunks, the cost adds up.
██╔████╔██║██║ ██║██║ ██║██║ ██║██║ ██║ ██║███████╗
TNT Sports’ contract expires at the end of next season