NotoSans CN/JP Glyph Test

All previews use only the bundled font — no fallback stack. Verification checks the font file and confirms the browser is rendering from it (no swap). Serve locally: python3 -m http.server 8000 · Live: notosans-glyph-test.pages.dev

Type anything

Your input
Rendered in NotoSans CN/JP

Definitive proof pixel test

NotoSans can look similar to your system Japanese font — that is normal. This test compares pixel data, not appearance. If the browser matches the .ttf file and differs from the system font, it is definitively using the bundled font.

Test string

UI Strings —

Key English Japanese Verification

Suspicious / Garbled Strings review

These appeared as separate rows in your source data — likely translation errors, not font issues.

String Rendered Verification

All Unique Characters (Japanese only)

For Qt developers important

Qt metadata issue — fixed in V3-qt-fixed files. Family name is now unified as NotoSans CN JP with correct subfamilies (Light / Regular / Medium). Use the V3 files in this folder — older V2-fixed files have been removed.

Exact family names (from font file)

Qt checklist

  • Load each .ttf with QFontDatabase::addApplicationFont()
  • Use the exact name returned by QFontDatabase::applicationFontFamilies(id)
  • Subfamilies are Light / Regular / Medium — use family NotoSans CN JP
  • Set weight explicitly: Light=300, Regular=400, Medium=500
  • Ensure UI strings are UTF-8 (check QString::fromUtf8 / translation file encoding)
  • Disable font fallback during testing: QFont::NoFontMerging (Qt 6) or verify with QFontInfo(font).family()
  • Confirm the deployed build ships the V3-qt-fixed.ttf files, not an older subset

Minimal Qt test (copy to reproduce)

Share with developers

Download verification report with all character codes and font metadata.