Copyglyph

CJK Compatibility

All code points in the CJK Compatibility block.

U+3358
U+3359
U+335A
U+335B
U+335C
U+335D
U+335E
U+335F
U+3360
U+3361
U+3362
U+3363
U+3364
U+3365
U+3366
U+3367
U+3368
U+3369
U+336A
U+336B
U+336C
U+336D
U+336E
U+336F
U+3370
U+3371
U+3372
U+3373
U+3374
U+3375
U+3376
U+3377
U+3378
U+3379
U+337A
U+337B
U+337C
U+337D
U+337E
U+337F
U+3380
U+3381
U+3382
U+3383
U+3384
U+3385
U+3386
U+3387
U+3388
U+3389
U+338A
U+338B
U+338C
U+338D
U+338E
U+338F
U+3390
U+3391
U+3392
U+3393
U+3394
U+3395
U+3396
U+3397
U+3398
U+3399
U+339A
U+339B
U+339C
U+339D
U+339E
U+339F

Tips

  • Ensure font fallback supports CJK Compatibility glyphs and use a broad font stack.
  • Normalize text consistently (NFC recommended) to avoid mismatches between compatibility characters and their intended glyphs.
  • Test rendering across environments where legacy fonts or systems may not include CJK Compatibility glyphs.
  • Document any usage constraints and provide clear fallbacks when a glyph is unavailable.
  • Avoid relying on compatibility characters for layout, and prefer explicit character choices or modern alternatives when possible.

The CJK Compatibility block contains characters that map to older or visually similar forms used in East Asian text pipelines. It is commonly encountered in legacy data and in interfaces that must interoperate with historical encoding schemes. For most new content, prefer unambiguous code points and rely on standard Unicode normalization to keep text stable.

Typical usage involves ensuring rendering compatibility across platforms and tools, and understanding how these characters relate to their standard counterparts. Pitfalls include duplicate or conflicting representations across fonts and input methods. For a broader view of related typographic elements, see Geometric shapes, Arrows, Currency symbols, and Box drawing.