Skip to content

Main content

Romanization Token Ambiguity Count Tool

Count collisions in a supplied romanization mapping, without generating linguistic equivalences.

Loading tool…

Description

Count romanized labels shared by different source tokens.

Language and manuscript records use explicit source labels, scripts, era-year conventions and text/area units. A literal split, Unicode slot or page-area calculation preserves supplied notation without resolving pronunciation, historical dates, manuscript identity or conservation needs.

Count romanized labels shared by different source tokens.

When to use this tool

Use Romanization Token Ambiguity Count when checking the stated language, manuscript, era-label or Unicode convention.

How to use the tool and how it works

  1. Enter sourceTokens, romanizedTokens. Follow any array-alignment requirements below. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read ambiguousRomanizations, collidingSourceTokens. Use the output convention below.

Count romanized labels shared by different source tokens. Require aligned arrays; group distinct source strings by romanized string, count ambiguous groups and sum their distinct-source counts.1

Input fieldMeaning and unitsAccepted input
sourceTokensSource TokensRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
romanizedTokensRomanized TokensRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
ambiguousRomanizationsAmbiguous RomanizationsRequired. Safe integer.
collidingSourceTokensColliding Source TokensRequired. Safe integer.
json
{
  "input": {
    "sourceTokens": [
      "甲",
      "乙",
      "丙"
    ],
    "romanizedTokens": [
      "a",
      "a",
      "b"
    ]
  },
  "output": {
    "ambiguousRomanizations": 1,
    "collidingSourceTokens": 2
  }
}

Limitations and assumptions

  • Literal collisions do not resolve pronunciation, script identity, transliteration quality or a language-specific standard.
  • 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

Inspect the original text/manuscript and its documented language, edition, calendar and encoding conventions for substantive linguistic, historical or conservation interpretation.

References

  1. Calculation and input contract: asian-studies/romanization-token-ambiguity-count — tool.io

Similar or alternative tools