Copyglyph

Punctuation, Other (Po)

All code points with General_Category Po.

؝
U+61D
؞
U+61E
؟
U+61F
٫
U+66B
٬
U+66C
٭
U+66D
U+964
U+965
U+970
U+A673
U+A67E
§
U+A7
U+A8F8
U+A8F9
U+A8FA
U+A8FC
U+A92E
U+B6
·
U+B7
U+FE14
U+FE30
U+FE45
U+FE46
U+FE49
U+FE4A
U+FE4B
U+FE4C
U+FE52
U+FE56
U+FE5F
U+FE60
U+FE61
U+FE68
U+FE6B
U+FF03
U+FF06
U+FF0A
U+FF0C
U+FF0F
U+FF1F
U+FF20
U+FF3C
U+FF65

Tips

  • Clearly define the Po category for points that are not letters, numbers, or symbols but still punctuation-like marks; document criteria for consistent classification.
  • Use data-driven Unicode files to classify code points rather than hand-coding lists; keep mappings centralized and versioned.
  • Account for typography and language context; some Po forms vary by locale and font, affecting rendering and word boundaries.
  • Ensure accessibility with clear semantics and predictable behavior in assistive tech; test with screen readers and keyboard navigation.
  • Validate across platforms and fonts; check rendering in common editors, browsers, and OS-level typography before release.

Punctuation, Other (Po) covers marks that punctuate text but do not fall into the standard symmetric punctuation or symbol classes. It often sits between language scripts and typographic design, guiding rendering rules and search behavior in multilingual content. In practice, Po points are used by font developers, localization pipelines, and text engines to keep punctuation handling predictable across contexts.

Typical usage involves tagging unusual or language-agnostic punctuation so tooling can apply correct shaping, breaking, and rendering decisions. Pitfalls include overgeneralizing Po as merely “special symbols,” which can misclassify characters that influence line breaking or text flow. Historically, designers have sought stable, cross-platform conventions for punctuation to improve interoperability and readability across languages and scripts. For related topics, see Arrows block and Geometric shapes block.