Hangul Jamo Composition Count
Resolve exact modern Hangul L/V/optional-T composition and per-syllable jamo counts after NFC, not random Hangul generation or archaic/conjoining-jamo inventory inference.
Description
A modern Hangul syllable contains leading and vowel jamo plus an optional trailing jamo.
A modern Hangul syllable contains leading and vowel jamo plus an optional trailing jamo. Unicode composition gives an exact decomposition.1, 2
Enter text that becomes exclusively modern precomposed Hangul syllables after NFC. Return syllable count, per-syllable2/3 jamo counts, conjoining-jamo strings and total.
When to use Hangul Jamo Composition Count
Use Hangul Jamo Composition Count when you need to evaluate the supplied records under the calculation and evidence rules below. Archaic, standalone or unmatched jamo and other characters fail. No linguistic segmentation beyond modern Unicode syllables is inferred.
Prepare explicit text tokens, annotated language observations, caller mappings or a supported locale as requested. Preserve source evidence and the stated Unicode counting convention.
How to use Hangul Jamo Composition Count and understand its results
- Prepare explicit text tokens, annotated language observations, caller mappings or a supported locale as requested. Preserve source evidence and the stated Unicode counting convention.
- Enter syllableText using the field table and calculation rules, then run the tool.
- Read normalizedHangulSyllableCount, perSyllableJamoCounts, decomposedJamoStrings, totalComposingJamoCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| syllableText | Syllable text | string | Required |
Enter text that becomes exclusively modern precomposed Hangul syllables after NFC. Return syllable count, per-syllable2/3 jamo counts, conjoining-jamo strings and total.
s=codepoint−AC00; L=floor(s/588); V=floor((s mod588)/28); T=s mod28 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| normalizedHangulSyllableCount | Normalized hangul syllable count | number |
| perSyllableJamoCounts | Per syllable jamo counts | list of number |
| decomposedJamoStrings | Decomposed jamo strings | list of string |
| totalComposingJamoCount | Total composing jamo count | number |
{
"input": {
"syllableText": "가각"
},
"output": {
"normalizedHangulSyllableCount": 2,
"perSyllableJamoCounts": [
2,
3
],
"decomposedJamoStrings": [
"가",
"각"
],
"totalComposingJamoCount": 5
}
}Limitations and assumptions
Archaic, standalone or unmatched jamo and other characters fail. No linguistic segmentation beyond modern Unicode syllables is inferred.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Hebrew Final-Forms Letter Set: Five Hebrew letters have word-final forms. Explicit word tokens make the boundary used for normalization clear. For a complementary task, use RTL/LTR Script Direction Classifier: Script-level direction counts provide a limited text inventory. Actual Unicode bidirectional layout also depends on marks, numbers and formatting controls.
Further background: Unicode Standard: Hangul Composition and Decomposition.
References
-
Hangul Jamo Composition Count — tool.io
-
Unicode Standard: Hangul Composition and Decomposition — Unicode Consortium
Similar or alternative tools
- Hebrew Final-Forms Letter Set
Five Hebrew letters have word-final forms. Explicit word tokens make the boundary used for normalization clear.
- RTL/LTR Script Direction Classifier
Script-level direction counts provide a limited text inventory. Actual Unicode bidirectional layout also depends on marks, numbers and formatting controls.