Copyglyph

Basic Latin

All code points in the Basic Latin block.

U+0

U+1

U+10

U+11

U+12

U+13

U+14

U+15

U+16

U+17

U+18

U+19

U+1A

U+1B

U+1C

U+1D

U+1E

U+1F

U+2
U+20
!
U+0021
"
U+22
#
U+23
$
U+24
%
U+25
&
U+0026
'
U+27
(
U+28
)
U+29
*
U+2A
+
U+002B
,
U+2C
-
U+2D
.
U+2E
/
U+2F

U+3
0
U+30
1
U+31
2
U+32
3
U+33
4
U+34
5
U+35
6
U+36
7
U+37
8
U+38
9
U+39
:
U+3A
;
U+3B
<
U+3C
=
U+3D
>
U+3E
?
U+003F

U+4
@
U+40
A
U+41
B
U+42
C
U+43
D
U+44
E
U+45
F
U+46
G
U+47
H
U+48
I
U+49
J
U+4A
K
U+4B
L
U+4C
M
U+4D
N
U+4E
O
U+4F

U+5
P
U+50
Q
U+51

Tips

  • Use Basic Latin as the default for UI text and data interchange to maximize compatibility.
  • Ensure UTF-8 encoding everywhere and validate round-tripping of Basic Latin content.
  • Test rendering across fonts and platforms; provide sensible fallbacks for missing glyphs.
  • Prefer plain ASCII in code samples, data payloads, and identifiers to avoid encoding issues.
  • Document any deviations when you encounter non-Basic-Latin characters and establish a consistent handling policy.

Basic Latin covers the standard ASCII range: common letters, digits, and punctuation. It is widely supported and often used as a baseline for UI text, identifiers, and data formats.

In practice, you’ll mix Basic Latin with other scripts as needed, but plan for graceful fallbacks and clear user messaging when non-Basic-Latin content is introduced. A long history of ASCII-driven systems means many developers rely on predictable, portable text. When you design or implement, remember that pitfalls include inconsistent encoding handling, font substitutions, and locale-related quirks. For related concerns, see Geometric shapes block, Arrows block, Currency symbols, and Box drawing block.