/*
 * Chinese-page font override, loaded after styles.css on zh/index.php only.
 *
 * The English page's display/body fonts (Bricolage Grotesque, DM Sans) are
 * loaded from Google Fonts and don't include CJK glyphs anyway, so Chinese
 * text would fall back to the OS font regardless. Google's font domains are
 * also unreliable from mainland China. Rather than loading that stylesheet
 * for nothing, the Chinese page skips it entirely and uses native system
 * fonts here, which render faster and look native on every platform.
 */
:root {
  --f-display: -apple-system, BlinkMacSystemFont, 'PingFang SC', 'Microsoft YaHei', 'Heiti SC', 'Segoe UI', system-ui, sans-serif;
  --f-body: -apple-system, BlinkMacSystemFont, 'PingFang SC', 'Microsoft YaHei', 'Heiti SC', 'Segoe UI', system-ui, sans-serif;
  --f-mono: ui-monospace, 'SFMono-Regular', Menlo, Consolas, 'Microsoft YaHei', monospace;
}

/* Slightly looser letter-spacing reads better for Han characters than the
   tight tracking tuned for the Latin display face. */
h1, h2, h3, h4, .brand__word { letter-spacing: normal; }
.eyebrow, .kicker, .era__step, .proc__kick { letter-spacing: .04em; }

/* Han text can break between any two characters, which splits words like 链/接
   in narrow columns. Headlines wrap their phrases in .nb: as inline-blocks a
   phrase moves to the next line whole when it fits, and only wraps inside when
   the column is narrower than the phrase itself, so it can never overflow.
   The slightly smaller hero size keeps each clause on one line on desktop. */
.nb { display: inline-block; }
h2, h3, h4 { text-wrap: balance; line-height: 1.3; }
.slide__title { font-size: clamp(2.2rem, 4.4vw, 3.75rem); line-height: 1.2; }
.section__head h2 { line-height: 1.22; }
.snap h3 { font-size: 1.25rem; }
