Description
Return romanization/source Unicode-code-point length ratio.
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.
Return romanization/source Unicode-code-point length ratio.
When to use this tool
Use Romanization Length Expansion Factor when checking the stated language, manuscript, era-label or Unicode convention.
How to use the tool and how it works
- Enter source, romanized. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sourceLength, romanizedLength, ratio, defined. Inspect defined before interpreting the associated values.
Return romanization/source Unicode-code-point length ratio. Count both strings by code points; ratio divides by source count or is zero with defined false for empty source.1
Unicode code points, UTF-16 code units and graphemes are different counting units. Precomposed modern Hangul syllables also have an algorithmic trailing-jamo slot, distinct from linguistic analysis.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| source | Source | Required. Text; maximum UTF-16 length 8192. |
| romanized | Romanized | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sourceLength | Unicode code-point count, not UTF-16 code units or graphemes. | Required. Safe integer. |
| romanizedLength | Romanized Length | Required. Safe integer. |
| ratio | Ratio | Required. Finite number. |
| defined | Whether the stated denominator or information basis supports this value; inspect placeholders before interpretation. | Required. Boolean. |
{
"input": {
"source": "東京",
"romanized": "Tokyo"
},
"output": {
"sourceLength": 2,
"romanizedLength": 5,
"ratio": 2.5,
"defined": true
}
}Limitations and assumptions
- Code points are not graphemes or syllables; no romanization quality, linguistic expansion or identity equivalence is inferred.
- 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
Similar or alternative tools
- Romanization Token Ambiguity Count
Count romanized labels shared by different source tokens.
- Public Text Syllable Mark Count
Count supplied single-code-point marks in text.