Description
Look up grapheme literally, returning its paired form and found true, or the unchanged grapheme with found false.
Unicode text can be counted as code points, UTF-16 units, encoded bytes, or grapheme clusters. A literal character transformation follows a specific mapping and may preserve distinctions that a broader normalization would remove.
Look up grapheme literally, returning its paired form and found true, or the unchanged grapheme with found false.
When to use this tool
Use Authorized Grapheme Case Variant Token when you need one explicitly bounded Unicode mapping, count, or encoding component.
How to use the tool and how it works
- Enter grapheme, sourceForms, authorizedForms. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read found, authorized. Inspect found before interpreting the associated values.
Require aligned sourceForms and authorizedForms with distinct sourceForms. Look up grapheme literally, returning its paired form and found true, or the unchanged grapheme with found false.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| grapheme | Grapheme | Required. Text; maximum UTF-16 length 8192. |
| sourceForms | Source Forms | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| authorizedForms | Authorized Forms | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| found | Whether the literal lookup found a matching input record. | Required. Boolean. |
| authorized | Mapped literal form when found, otherwise the original input grapheme; this is not an authorization verdict. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"grapheme": "a",
"sourceForms": [
"a"
],
"authorizedForms": [
"A"
]
},
"output": {
"found": true,
"authorized": "A"
}
}Limitations and assumptions
- No Unicode normalization, grapheme segmentation, language-aware casing, or verification of authorization is performed.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Choose normalization and comparison rules for the intended language and preserve the original text when creating a search variant.
References
Similar or alternative tools
- Consented Name Search Key Flag
Set includeInSearch only when consented and not withdrawn, returning suppliedKey when included and an empty string otherwise.
- Historical Unit Symbol Token
Return literal membership and its zero-based index, or index -1 when absent.