Japanese text is set with Latin typography rules
Site-wide · mobile
The only declared fonts are Jost, Helvetica Neue and Arial, all Latin typefaces. Every kana and kanji falls back to whatever the device has: Hiragino on Apple devices, Yu Gothic or Meiryo on Windows (Yu Gothic Regular renders thin and faint there [8]), Noto on Android. On top of that, Japanese is tracked at −0.03em (−0.42px on body copy) and the product name at −0.05em (−1.65px), a Latin display technique that squeezes full-width characters together. Body copy runs at line-height 1.3, the product name at 1.12. Japanese readers perceive this as cramped and “translated” without knowing why. Every Japanese benchmark we measured declares a Japanese face, and none of them uses negative tracking on Japanese (section 03).
DONE RIGHT IN JAPAN
- IKEA Japan keeps its global design system and adds Noto Sans JP after its brand font, with normal tracking. It's the clearest precedent that localising type doesn't break a global brand.
- unico sets body copy in Noto Sans JP at 14px with line-height up to 1.8 and +0.6px tracking.
PROPOSAL
- One
:lang(ja)CSS layer:"Jost", "Noto Sans JP", "Hiragino Sans", Meiryo, sans-serif. Jost keeps rendering Latin letters and numerals, so the brand font stays. - Tracking 0 to +0.04em for Japanese. Keep body line-height at 1.5 or more and longer copy around 1.7; lift the product name from 1.12 to at least 1.4. Line height on its own is a secondary issue: Apple and Dyson use about 1.4.
If HQ asks “Jost is our global font”: it stays. A Japanese face is added after it in the stack for kana and kanji, exactly as IKEA does.
If HQ asks “LOWYA uses small 12px text too”: it does, as a dense catalogue retailer. But LOWYA names Japanese fonts and never uses negative tracking. Size isn't the main issue here; the missing Japanese font, the tracking and the broken words are.