Pigpen Masonic Decoder
Encode explicit pigpen canonical ASCII symbol IDs, undotted grid A–I, dotted J–R, undotted X S–V and dotted W–Z; not visual glyph/font inference. Classical educational encoding only; not secure encryption, no hidden normalization or inferred key.
Description
A textual Pigpen token stream requires an agreed symbol convention.
A textual Pigpen token stream requires an agreed symbol convention.1
Decoding exact tokens does not recognize an image of handwritten cipher marks. Use Pigpen Masonic Decoder to evaluate the supplied inputs under the specific model below.
When to use Pigpen Masonic Decoder
Use Pigpen Masonic Decoder to evaluate the supplied inputs under the specific model below. Choose the intended encoding, alphabet or check and keep the exact character, key and measurement conventions described below.
How to use Pigpen Masonic Decoder and understand its results
- Choose the intended encoding, alphabet or check and keep the exact character, key and measurement conventions described below.
- Enter Text using the field table and validation rules below, then run the tool.
- Read Transformed and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| text | Text | string | Required; constraints below |
Enter at most 16384 characters in the exact supported Pigpen token convention, with single spaces between tokens. Map each G or X token, including any dot, back to its uppercase A–Z letter. Empty input returns empty text; repeated spaces and unsupported tokens fail. This recognizes textual tokens rather than images of Pigpen glyphs.
plaintext = concatenate fixedInversePigpenTable[token] for each single-space-separated token Field order, units and branch conditions follow the implementation explanation above.
| Output field | Meaning | Value type |
|---|---|---|
| transformed | Transformed | string |
{
"input": {
"text": "G1 G2 X4."
},
"output": {
"transformed": "ABZ"
}
} Limitations and assumptions
Decoding exact tokens does not recognize an image of handwritten cipher marks. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
This educational transformation or format check does not establish modern cryptographic confidentiality, authentication or key security.
Alternative or Complementary methods
Use Multi-Tap Keypad Decoder for a related task: Multi-tap decoding uses a fixed keypad grouping and explicit token boundaries.
Use Pigpen Masonic Encoder for a related task: Pigpen notation represents letters with grid and cross forms.
References
-
Pigpen Masonic Decoder — tool.io
Similar or alternative tools
- Multi-Tap Keypad Decoder
Multi-tap decoding uses a fixed keypad grouping and explicit token boundaries.
- Pigpen Masonic Encoder
Pigpen notation represents letters with grid and cross forms.