剖析器(Parser)報錯、Webhook 簽章驗證失敗以及 SQL 查詢未命中,往往源於在終端機模擬器或程式碼編輯器中渲染效果完全相同(甚至完全不可見)的特殊字元。假設從文件入口網站或即時通訊軟體中複製了一段環境變數,肉眼看起來與 api_key=prod 完全一致:
Visual rendering: api_key=prod
String.length: 14 (expected 12)
UTF-8 byte length: 19 bytes (expected 12 bytes)
將這段長度為 14 的字串放入 Unicode 字元檢測器中執行,就能立即揪出潛藏在看似純 ASCII 文字中的三處異常:開頭的位元組順序標記(<BOM>)、頂替拉丁字母 a 的西里爾同形字,以及夾在中間的零寬空格(<ZWSP>):
[
{
"index": 0,
"badge": "<BOM>",
"codePoint": "U+FEFF",
"name": "ZERO WIDTH NO-BREAK SPACE",
"category": "Cf (Format)",
"block": "Arabic Presentation Forms-B",
"utf8Hex": "EF BB BF",
"utf16BE": "FE FF",
"utf16LE": "FF FE",
"warning": "Invisible zero-width format character"
},
{
"index": 1,
"glyph": "а",
"codePoint": "U+0430",
"name": "CYRILLIC SMALL LETTER A",
"category": "Ll (Lowercase Letter)",
"block": "Cyrillic",
"utf8Hex": "D0 B0",
"utf16BE": "04 30",
"utf16LE": "30 04",
"warning": "Confusable homoglyph for Latin U+0061 ('a')"
},
{
"index": 2,
"glyph": "p",
"codePoint": "U+0070",
"name": "LATIN SMALL LETTER P",
"category": "Ll (Lowercase Letter)",
"block": "Basic Latin",
"utf8Hex": "70",
"utf16BE": "00 70",
"utf16LE": "70 00",
"warning": null
},
{
"index": 8,
"badge": "<ZWSP>",
"codePoint": "U+200B",
"name": "ZERO WIDTH SPACE",
"category": "Cf (Format)",
"block": "General Punctuation",
"utf8Hex": "E2 80 8B",
"utf16BE": "20 0B",
"utf16LE": "0B 20",
"warning": "Invisible zero-width format character"
}
]
此外,本檢測器還能清晰解釋為什麼複合碼位 Emoji 在不同執行階段環境中會回報截然不同的字串長度。例如檢測單個視覺可見的工程師 Emoji 👨💻 時,工具會展示出它實際上是由 <ZWJ>(U+200D)連接的 3 個純量碼位組成,在 JavaScript 中佔用 5 個 UTF-16 編碼單元,而在 UTF-8 中佔用 11 個位元組:
Grapheme clusters (UAX #29): 1 -> [ "👨💻" ]
Unicode scalar code points: 3 -> U+1F468 (Man) + U+200D (<ZWJ>) + U+1F4BB (Laptop)
UTF-16 code units (.length): 5 -> D83D DC68 + 200D + D83D DCBB
UTF-8 encoded bytes: 11 -> F0 9F 91 A8 + E2 80 8D + F0 9F 92 BB