Skip to content

Main content

Unicode Keycap Sequence Base Token Tool

Calculate unicode keycap sequence base token from explicit caller-supplied inputs.

Loading tool…

Description

Check text for one digit, hash, or asterisk followed by optional U+FE0F and U+20E3.

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.

Check text for one digit, hash, or asterisk followed by optional U+FE0F and U+20E3.

When to use this tool

Use Unicode Keycap Sequence Base Token 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 text. 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 valid, base, variationSelector. Inspect valid, variationSelector before interpreting the associated values.

Check text for one digit, hash, or asterisk followed by optional U+FE0F and U+20E3. Return valid, its base when valid, and whether that accepted sequence includes the selector.1

Input fieldMeaning and unitsAccepted input
textTextRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
validWhether this tool’s specific rule passes, not a broader approval.Required. Boolean.
baseBaseRequired. Text; maximum UTF-16 length 8192.
variationSelectorVariation SelectorRequired. Boolean.
json
{
  "input": {
    "text": "1️⃣"
  },
  "output": {
    "valid": true,
    "base": "1",
    "variationSelector": true
  }
}

Limitations and assumptions

  • Malformed text returns empty base and false selector status. This is sequence shape only, not full grapheme segmentation, emoji rendering, or font compatibility.
  • 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-keycap-sequence-base-token — tool.io

Similar or alternative tools