Skip to content

Main content

Disclosure Character Budget Gap Tool

Count Unicode code points against an explicit disclosure text budget; no legal adequacy determination.

Loading tool…

Description

Count disclosure Unicode code points and return budget-used as a signed gap.

Advertising records distinguish billable exposure, disclosure support, cyclic reporting windows, layout insets and supplied tax bases. A code-point budget or visibility-duration share does not establish readable or legally sufficient disclosure. Nominal geometry and costs require the intended platform and reporting conventions.

Count disclosure Unicode code points and return budget-used as a signed gap.

When to use this tool

Use Disclosure Character Budget Gap when checking the stated advertising layout, exposure, boundary or cost convention.

How to use the tool and how it works

  1. Enter disclosure, budget. 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 used, gap. Use the output convention below.

Require nonnegative whole character budget. Count disclosure Unicode code points and return budget-used as a signed gap.1

Code points, UTF-16 code units, canonical decomposition and case conversion are different operations. This helper follows its explicit local convention rather than linguistic analysis or rendered-text measurement.2

Input fieldMeaning and unitsAccepted input
disclosureDisclosureRequired. Text; maximum UTF-16 length 8192.
budgetBudgetRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
usedUnicode code-point count, not UTF-16 code units, grapheme clusters or rendered width.Required. Safe integer.
gapGapRequired. Safe integer.
json
{
  "input": {
    "disclosure": "Ad: paid",
    "budget": 12
  },
  "output": {
    "used": 8,
    "gap": 4
  }
}

Limitations and assumptions

  • Code points are not grapheme clusters or rendered width; this does not establish a legally adequate disclosure.
  • 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

Inspect actual rendered creatives and verified delivery/billing records, and consult applicable platform, advertising and tax requirements for real decisions.

References

  1. Calculation and input contract: advertising/disclosure-character-budget-gap — tool.io

  2. Unicode 17.0: encoding and normalization conventions — Unicode Consortium

Similar or alternative tools