Hebrew Final-Forms Letter Set
Normalize five Hebrew final forms at explicit unpointed word ends and medialize internal final letters, preserving caller word boundaries; no automatic morphology, niqqud processing or language identification.
Description
Five Hebrew letters have word-final forms.
Five Hebrew letters have word-final forms. Explicit word tokens make the boundary used for normalization clear.1
Enter nonempty unpointed Hebrew word tokens 1–128 letters. Normalize internal final letters to medial forms, then apply final form to a qualifying last letter; return words and changed flags.
When to use Hebrew Final-Forms Letter Set
Use Hebrew Final-Forms Letter Set when you need to evaluate the supplied records under the calculation and evidence rules below. Niqqud, punctuation and word segmentation are rejected or left to the caller; no morphology or language detection is performed.
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 Hebrew Final-Forms Letter Set 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 unpointedHebrewWords using the field table and calculation rules, then run the tool.
- Read normalizedFinalFormWords, wordChangedFlags. 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 |
|---|---|---|---|
| unpointedHebrewWords | Unpointed hebrew words | list of string | Required |
Enter nonempty unpointed Hebrew word tokens 1–128 letters. Normalize internal final letters to medial forms, then apply final form to a qualifying last letter; return words and changed flags.
medialize all ךםןףץ; finalize last כ/מ/נ/פ/צ Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| normalizedFinalFormWords | Normalized final form words | list of string |
| wordChangedFlags | Word changed flags | list of number |
{
"input": {
"unpointedHebrewWords": [
"מלכ",
"כף"
]
},
"output": {
"normalizedFinalFormWords": [
"מלך",
"כף"
],
"wordChangedFlags": [
1,
0
]
}
}Limitations and assumptions
Niqqud, punctuation and word segmentation are rejected or left to the caller; no morphology or language detection is performed.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Hangul Jamo Composition Count: A modern Hangul syllable contains leading and vowel jamo plus an optional trailing jamo. Unicode composition gives an exact decomposition. 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.
References
-
Hebrew Final-Forms Letter Set — tool.io
Similar or alternative tools
- Hangul Jamo Composition Count
A modern Hangul syllable contains leading and vowel jamo plus an optional trailing jamo. Unicode composition gives an exact decomposition.
- 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.