Description
Normalize each input to NFC, or to NFD followed by removal of every Unicode Mark when ignoreDiacritics.
A similarity term depends on the comparison universe, missing-value policy, treatment of repeated features, and normalization. A score can also have a caller-selected value when its mathematical denominator vanishes. Those conventions matter before interpreting a threshold or comparing methods.
Normalize each input to NFC, or to NFD followed by removal of every Unicode Mark when ignoreDiacritics.
When to use this tool
Use Textmatch Normalized Diacritic Policy when you need this particular comparison term, normalization, domain condition, or empty-result policy in a larger matching workflow.
How to use the tool and how it works
- Enter first, second, ignoreDiacritics. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read match, normalizedFirst, normalizedSecond. Inspect match before interpreting the associated values.
Normalize each input to NFC, or to NFD followed by removal of every Unicode Mark when ignoreDiacritics. Return both normalized strings and their exact match flag.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First | Required. Text; maximum UTF-16 length 8192. |
| second | Second | Required. Text; maximum UTF-16 length 8192. |
| ignoreDiacritics | Ignore Diacritics | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| match | Match | Required. Boolean. |
| normalizedFirst | Normalized First | Required. Text; maximum UTF-16 length 8192. |
| normalizedSecond | Normalized Second | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"first": "café",
"second": "cafe",
"ignoreDiacritics": true
},
"output": {
"match": true,
"normalizedFirst": "cafe",
"normalizedSecond": "cafe"
}
}Limitations and assumptions
- Case is preserved and runtime Unicode data apply. Mark removal is broader than accent removal in some scripts and is not universal transliteration, language equivalence, or safe identifier canonicalization.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Compare methods only after aligning feature definitions, missingness, empty policies, multiplicities, and normalizers. Use a complete comparison when the tool returns only one contribution or count check.
References
Similar or alternative tools
- Token Match Case Fold Policy Pair
Compare two tokens with an explicit ASCII-only case-folding policy.
- Token Overlap Multiplicity Policy
Count token intersection and union by minimum and maximum multiplicities when multiset, or by distinct presence otherwise.