Chyron Character per Line Limit Checker
Chyron line codepoint counts against caller limit; not glyph-width/layout or universal station template.
Description
Chyron Character per Line Limit Checker: return line codepoint counts, over limit line indices.
A chyron contains separate lines of screen text. A per-line text budget needs to be checked for every supplied line.
This tool returns line codepoint counts, over limit line indices. Use the stated units and model convention when interpreting these fields.
When to use this tool
Use this tool when the supplied inputs match the specific operation described above and you need a repeatable result under its stated convention.
- Check the supported input and output contract against an existing calculation or observation.
- Use the complete example to confirm units, selector spelling and result interpretation.
How to use the tool and how it works
- Enter every field in the input table using the stated units and the exact supported selector spelling where applicable.
- Run the tool. Correct input errors before interpreting an output.
- Read the result fields below; use accompanying flags and the stated sign, boundary or model convention when interpreting a number.
Count Unicode code points in each line and return the zero-based indices exceeding the caller's positive integer maximum.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| lines | Lines. | List of text values |
| callerMaximumCodepoints | Caller maximum codepoints. | Integer; from 1 to 1000000 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the following named result fields. |
| result.lineCodepointCounts | Line codepoint counts list, in the ordering described in the calculation. |
| result.overLimitLineIndices | Over limit line indices list, in the ordering described in the calculation. |
{
"input": {
"lines": [
"ABC",
"ABCDE"
],
"callerMaximumCodepoints": 4
},
"output": {
"result": {
"lineCodepointCounts": [
3,
5
],
"overLimitLineIndices": [
1
]
}
}
}Limitations and assumptions
- The tool does not measure rendered width, font metrics or safe broadcast framing.
- Every declared field is required and unexpected fields are rejected. Numeric inputs must be finite; input errors are distinct from a valid false result or an explicitly qualified output.
- Extremely large inputs and nonfinite or excessively large outputs are rejected. List positions reported by the tool use zero-based indices unless stated otherwise.
Alternative or Complementary methods
Check the underlying observations, units and conventions independently before using the result in a larger workflow. The tools listed below address nearby tasks; compare their inputs and scope before substituting one for this operation.
References
Similar or alternative tools
- Headline Character Count Limit Lookup
Qualified caller-reference registry: actual publication/platform, field/font/layout and current independently verified headline character limit; no universal maximum. Requires independently applicable source/context/date evidence; not an authoritative table, omitted predictive model, diagnosis, permission, safety or compliance determination.
- Push Notification Character Limit Platform Lookup
Qualified caller-reference registry: actual platform/device, notification field, encoding/layout and current independently verified notification limit. Requires independently applicable source/context/date evidence; not an authoritative table, omitted predictive model, diagnosis, permission, safety or compliance determination.