Skip to content

Main content

Unicode Script Extensions Cardinality Tool

Count caller-supplied Unicode Script_Extensions labels without embedding or inferring a Unicode database.

Loading tool…

Description

Count caller-supplied Unicode Script_Extensions labels without embedding or inferring a Unicode database.

Text positions can be measured in UTF-16 code units, Unicode code points, grapheme clusters, or modeled display columns. These coordinates are not interchangeable. Invisible markers and delimiter policies can also affect interpretation even when a string looks unchanged, so the chosen representation needs to stay explicit.

Count caller-supplied Unicode Script_Extensions labels without embedding or inferring a Unicode database.

When to use this tool

Use Unicode Script Extensions Cardinality when you need the stated marker, coordinate, delimiter, or normalization operation under an explicit text representation.

How to use the tool and how it works

  1. Enter suppliedScripts, unknown. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read uniqueScripts, cardinality, known. Inspect known before interpreting the associated values.

Deduplicate suppliedScripts in first-occurrence order, require every retained token nonempty, and return cardinality and known=!unknown.1

Input fieldMeaning and unitsAccepted input
suppliedScriptsSupplied ScriptsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
unknownUnknownRequired. Boolean.
Output fieldInterpretationReturned shape
uniqueScriptsUnique ScriptsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
cardinalityCardinalityRequired. Safe integer.
knownInverse of the supplied unknown flag, not a verified registry result.Required. Boolean.
json
{
  "input": {
    "suppliedScripts": [
      "Hira",
      "Kana",
      "Hira"
    ],
    "unknown": false
  },
  "output": {
    "uniqueScripts": [
      "Hira",
      "Kana"
    ],
    "cardinality": 2,
    "known": true
  }
}

Limitations and assumptions

  • Known is a supplied uncertainty flag, not evidence from a Unicode lookup. Scripts can still be returned when known is false; no script registry or text context is checked.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.

Alternative or Complementary methods

Choose the coordinate system required by the consumer. Use a full parser, renderer, or segmentation method when a local marker or delimiter rule cannot determine the complete text behavior.

References

  1. Calculation and input contract: text/unicode-script-extensions-cardinality — tool.io

Similar or alternative tools