Skip to content

Main content
Bookmark this: tool.io/encode/base45-two-byte-triple-symbols

Base45 Two Byte Triple Symbols Tool

Compute base45 two byte triple symbols from explicit bounded inputs.

Loading tool…

Description

Form value = 256*high+low and emit three symbols indexed by value modulo 45, floor(value/45) modulo 45 and floor(value/2025), using the Base45 alphabet.

A positional encoding separates numeric digit values, alphabet symbols and final-block padding. An alphabet lookup is not a whole-stream codec, and character count can differ from the number of source bytes represented.

Form value = 256*high+low and emit three symbols indexed by value modulo 45, floor(value/45) modulo 45 and floor(value/2025), using the Base45 alphabet.

When to use this tool

Use Base45 Two Byte Triple Symbols when checking one alphabet mapping or bounded encoding-padding term.

How to use the tool and how it works

  1. Enter high, low. 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 token. Use the output convention below.

Require whole high and low octets in [0,255]. Form value = 256*high+low and emit three symbols indexed by value modulo 45, floor(value/45) modulo 45 and floor(value/2025), using the Base45 alphabet.1

Base45 represents a two-octet group with three ordered alphabet symbols. Complete streams must handle their final group appropriately.2

Input fieldMeaning and unitsAccepted input
highHighRequired. Safe integer; minimum 0; maximum 255.
lowLowRequired. Safe integer; minimum 0; maximum 255.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "high": 65,
    "low": 66
  },
  "output": {
    "token": "BB8"
  }
}

Limitations and assumptions

  • This encodes exactly a two-byte group in least-significant Base45 digit order. Final one-byte groups and complete stream framing are not included.
  • 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 complete codec matching the intended alphabet and padding policy for real payloads and interoperability checks.

References

  1. Calculation and input contract: encode/base45-two-byte-triple-symbols — tool.io

  2. The Base45 data encoding: RFC 9285 — Internet Engineering Task Force

Similar or alternative tools

Support Tool.io