Description
Count cue-text code points against a supplied budget.
Performance planning separates cue text length, tempo, frame/time coordinates, prop counts and rehearsal budgets. Code points differ from displayed characters, and rest-bar duration assumes consistent beat definitions and constant tempo. A supplied count or geometric margin does not verify cue execution, accessibility, labor rules or safe stage operations.
Count cue-text code points against a supplied budget.
When to use this tool
Use Subtitle Super Title Cue Length when you already have cueText, maximumCodePoints and need to count cue-text code points against a supplied budget.
How to use the tool and how it works
- Enter cueText, maximumCodePoints. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read codePointCount, remainingBudget, fits. Inspect fits before interpreting the associated values.
Require nonnegative safe whole maximumCodePoints; count Array.from(cueText).length, return budget-count and count<=budget.1
A grapheme cluster can contain multiple code points. This code-point budget therefore differs from a user-perceived-character or rendered-width limit.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| cueText | Cue Text | Required. Text; maximum UTF-16 length 8192. |
| maximumCodePoints | Maximum Code Points | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| codePointCount | Array.from text length, distinct from grapheme clusters and display width. | Required. Safe integer. |
| remainingBudget | Remaining Budget | Required. Safe integer. |
| fits | Fits | Required. Boolean. |
{
"input": {
"cueText": "Hello world",
"maximumCodePoints": 20
},
"output": {
"codePointCount": 11,
"remainingBudget": 9,
"fits": true
}
}Limitations and assumptions
- Code points differ from grapheme clusters, glyphs and display width; no subtitle reading-time or accessibility standard is selected.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use the actual cue sheet, acquisition clock and tempo map for a complete timing plan. Review rendered text for width and reading time, and dimensioned sightlines or physical inventories for seating and prop questions that a scalar budget cannot settle.
References
-
Calculation and input contract: performing-arts/subtitle-super-title-cue-length — tool.io
-
Unicode 17.0: characters and encoding forms — Unicode Consortium
Similar or alternative tools
- convert/text-to-unicode-code-points
Represent every Unicode character as an uppercase U+ hexadecimal scalar value without splitting supplementary characters into surrogate halves.
- Unicode Escape Source Offset Shift
Shift a Unicode-source offset by a supplied number of source code units.