Copyglyph

Script: Common

All code points assigned to the Common script.

U+10FB
U+16EB
U+16EC
U+16ED
U+1735
U+1736
U+1802
U+1803
U+1805
U+1CD3
U+1CE1
U+1CE9
U+1CEA
U+1CEB
U+1CEC
U+1CEE
U+1CEF
U+1CF0
U+1CF1
U+1CF2
U+1CF3
U+1CF5
U+1CF6
U+1CF7
U+1CFA
𞲰
U+1ECB0
🃏
U+1F0CF
U+20
 
U+2000
U+2001
U+2002
U+2003
U+2004
U+2005
U+2006
U+2007
U+2008
U+2009
U+200A
U+200B
U+200E
U+200F
U+2010
U+2011
U+2012
U+2013
U+2014
U+2015
U+2016
U+2017
U+2019
U+201A
U+201B
U+201D
U+2020
U+2021
U+2022
U+2023
U+2024
U+2025
U+2027
U+2028
U+2029
U+202A
U+202B
U+202C
U+202D
U+202E
U+2030
U+2031
U+2032
U+2033

Tips

  • Define a clear scope for Common script usage in your project’s typography guidelines.
  • Validate rendering across major platforms and fonts to catch mismatches early.
  • Provide robust font stacks and sensible fallbacks for missing glyphs.
  • Keep script-aware APIs and text processing consistent to avoid mixups.
  • Document accessibility considerations, including contrast and screen reader behavior.

The Common script covers characters shared across multiple writing systems, serving as a general-purpose foundation for text. It is often used for UI labels, programming-oriented content, and mixed-language interfaces. Understanding its scope helps designers and developers avoid over- or under-committing resources.

Typical usage includes ensuring consistent rendering, predictable fallback handling, and clean fallback paths when fonts don’t support certain glyphs. Pitfalls include ambiguity about which characters should be treated as part of the script and subtle font-rendering differences that affect legibility. A broad historical trend has been toward universal text rendering that abstracts away individual scripts, while still exposing enough metadata for accurate display and accessibility.