Skip to content

Main content

Unicode Emoji Tag Terminator Sequence Check Tool

Check the black-flag tag-sequence structural form without asserting registry membership or rendered flag support.

Loading tool…

Description

Check the black-flag tag-sequence structural form without asserting registry membership or rendered flag support.

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 the black-flag tag-sequence structural form without asserting registry membership or rendered flag support.

When to use this tool

Use Unicode Emoji Tag Terminator Sequence Check 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, tagCount. Inspect valid before interpreting the associated values.

Check for black-flag base U+1F3F4, one or more printable tag characters U+E0020–E007E, and final cancel tag U+E007F. Return valid and tagCount as the code-point length minus two, floored at zero.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.
tagCountCode-point length minus two, floored at zero, even when valid is false.Required. Safe integer.
json
{
  "input": {
    "text": "🏴󠁧󠁢󠁿"
  },
  "output": {
    "valid": true,
    "tagCount": 2
  }
}

Limitations and assumptions

  • TagCount is reported even for invalid sequences. This shape check does not verify an assigned subdivision flag, emoji validity beyond the rule, or rendering support.
  • 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-emoji-tag-terminator-sequence-check — tool.io

Similar or alternative tools