Description
Decode one RFC 2047 Q-space token.
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 RFC 2047 Q-space token.
When to use this tool
Use RFC 2047 Q Underscore Space Token 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 decoded. Use the output convention below.
Decode one RFC 2047 Q-space token. Require token to be exactly underscore and return one ASCII space.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 |
|---|---|---|
| decoded | Decoded | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "_"
},
"output": {
"decoded": " "
}
}Limitations and assumptions
- This special rule concerns encoded-word Q text, not ordinary quoted-printable bodies or arbitrary underscores.
- 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
- RFC 2047 Encoded Word Header Fields
Split a restricted MIME encoded-word into header fields.
- Mime Q Hex Escape Octet
Decode one MIME Q hexadecimal escape to an octet.