Arabic Three-Letter Root Share

Audit letter lengths of caller already identified Arabic roots, ignoring combining vowel marks and retaining nontriliteral roots; does not extract roots from words or infer language-wide share.

Description

Root-length shares describe an already identified Arabic-root sample.

Root-length shares describe an already identified Arabic-root sample. Counting letters is separate from extracting roots from words.^[1]

Enter nonempty caller-identified Arabic-letter roots with optional combining marks. NFC-normalize/remove marks, reject other characters, count Unicode letters and return lengths, three-letter count, total and percentage.

When to use Arabic Three-Letter Root Share

Use Arabic Three-Letter Root Share when you need to evaluate the supplied records under the calculation and evidence rules below. No morphology, etymology or language-wide triliteral share 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 Arabic Three-Letter Root Share 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 callerIdentifiedArabicRootTokens using the field table and calculation rules, then run the tool.
Read observedRootLetterCounts, threeLetterRootCount, totalObservedRootCount, threeLetterRootSharePercent. 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
callerIdentifiedArabicRootTokens	Caller identified arabic root tokens	list of string	Required

triliteral%=100×count(length3)/observed root count

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
observedRootLetterCounts	Observed root letter counts	list of number
threeLetterRootCount	Three letter root count	number
totalObservedRootCount	Total observed root count	number
threeLetterRootSharePercent	Three letter root share percent	number

json

{
  "input": {
    "callerIdentifiedArabicRootTokens": [
      "كتب",
      "دحرج",
      "قُرْأ"
    ]
  },
  "output": {
    "observedRootLetterCounts": [
      3,
      4,
      3
    ],
    "threeLetterRootCount": 2,
    "totalObservedRootCount": 3,
    "threeLetterRootSharePercent": 66.66666666666667
  }
}

Limitations and assumptions

No morphology, etymology or language-wide triliteral share is inferred.

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 Romance Latin Root Percent Estimate: An origin-share inventory needs separate denominators for classified and all observed weight. Unknown origin should remain visible. For a complementary task, use Letter Frequency Rank By Language Lookup Table: Letter-frequency ranks describe the supplied corpus and alphabet. Ties use competition rank rather than an arbitrary alphabet order.

References

Arabic Three-Letter Root Share — tool.io

Similar or alternative tools

Romance Latin Root Percent Estimate
An origin-share inventory needs separate denominators for classified and all observed weight. Unknown origin should remain visible.
Letter Frequency Rank By Language Lookup Table
Letter-frequency ranks describe the supplied corpus and alphabet. Ties use competition rank rather than an arbitrary alphabet order.