Description
Split a supplied romanized name at explicit separators.
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.
Split a supplied romanized name at explicit separators.
When to use this tool
Use Romanized Name Syllable Boundary when checking the stated language, manuscript, era-label or Unicode convention.
How to use the tool and how it works
- Enter name, suppliedSeparator. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read parts, boundaryOffsets. Use the output convention below.
Split a supplied romanized name at explicit separators. Require nonempty separator; parts preserves literal split results, boundaryOffsets gives zero-based UTF-16 offsets at each separator start.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 |
|---|---|---|
| name | Name | Required. Text; maximum UTF-16 length 8192. |
| suppliedSeparator | Supplied Separator | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| parts | Parts | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| boundaryOffsets | Zero-based UTF-16 code-unit positions at separator starts, not linguistic syllable boundaries. | Required. Array of safe integer; maximum items 256. |
{
"input": {
"name": "An-na-li",
"suppliedSeparator": "-"
},
"output": {
"parts": [
"An",
"na",
"li"
],
"boundaryOffsets": [
2,
5
]
}
}Limitations and assumptions
- Empty parts are retained; no linguistic syllabification, romanization standard or identity resolution 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
Inspect the original text/manuscript and its documented language, edition, calendar and encoding conventions for substantive linguistic, historical or conservation interpretation.
References
-
Calculation and input contract: asian-studies/romanized-name-syllable-boundary — tool.io
-
Unicode 17.0: encoding forms and Hangul algorithms — Unicode Consortium
Similar or alternative tools
- Public Text Syllable Mark Count
Count supplied single-code-point marks in text.
- Romanization Token Ambiguity Count
Count romanized labels shared by different source tokens.