Description
Decode one MIME Q hexadecimal escape to an octet.
Escaping and token decoding depend on the surrounding format. Form-data plus signs, MIME Q underscores, quoted-printable octets and quoted CSV fragments have different meanings even when their text looks similar.
Decode one MIME Q hexadecimal escape to an octet.
When to use this tool
Use Mime Q Hex Escape Octet when decoding one explicitly supported format fragment.
How to use the tool and how it works
- Enter token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read octet. Use the output convention below.
Decode one MIME Q hexadecimal escape to an octet. Require equals plus exactly two case-insensitive hexadecimal digits; return their numeric value.1
Q-encoded header words give underscore a space meaning; encoded-word syntax alone does not perform charset conversion or complete header parsing.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| octet | One numeric octet, from 0 through 255. | Required. Safe integer. |
{
"input": {
"token": "=3D"
},
"output": {
"octet": 61
}
}Limitations and assumptions
- Underscore-space handling and charset conversion are separate; this is not a full encoded-word decoder.
- 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.
Alternative or Complementary methods
Use the full format-specific parser for framing, context, charset conversion and complete data validation.
References
Similar or alternative tools
- Quoted Printable Hex Pair Octet
Decode one quoted-printable hexadecimal octet token.
- RFC 2047 Q Underscore Space Token
Decode one RFC 2047 Q-space token.