When writing lexers, inspecting TCP packet dumps, or configuring serial and terminal I/O, developers constantly translate between raw byte values and symbolic representations. Below is a reference snapshot of the highest-frequency anchor rows across C0 controls (0–31, 127), printable 7-bit US-ASCII (32–126), and Extended ISO-8859-1 Latin-1 (128–255):
Dec Hex Oct Binary Glyph / Mnemonic Caret C / JS Escape HTML Entity
--- ---- --- -------- ---------------- ----- ------------- -----------
0 0x00 000 00000000 <NUL> (Null) ^@ \0 �
9 0x09 011 00001001 <HT> (Tab) ^I \t 	
10 0x0A 012 00001010 <LF> (Line Feed) ^J \n
13 0x0D 015 00001101 <CR> (Return) ^M \r
27 0x1B 033 00011011 <ESC> (Escape) ^[ \x1B 
32 0x20 040 00100000 <SP> (Space) - " "  
48 0x30 060 00110000 0 - 0 0
65 0x41 101 01000001 A - A A
97 0x61 141 01100001 a - a a
126 0x7E 176 01111110 ~ - ~ ~
127 0x7F 177 01111111 <DEL> (Delete) ^? \x7F 
160 0xA0 240 10100000 <NBSP> - \xA0
169 0xA9 251 10101001 © - \xA9 ©
255 0xFF 377 11111111 ÿ - \xFF ÿ
Practical Protocol Lookup Examples
Mapping raw wire bytes against the table immediately clarifies protocol framing and terminal control sequences:
1. HTTP/1.1 Header Terminator (RFC 9112):
Hex bytes: 0D 0A 0D 0A
Mnemonics: <CR><LF><CR><LF>
Escapes: "\r\n\r\n" (Decimal: 13, 10, 13, 10)
2. ANSI CSI Green Terminal Prompt:
Hex bytes: 1B 5B 33 32 6D
Decoded: <ESC> (0x1B / ^[) + '[' (0x5B) + '3' (0x33) + '2' (0x32) + 'm' (0x6D)
JS literal: "\x1b[32m"