/* Ageshio Japan — the ONE @font-face exception D5/D9 allow (V4 rebuild, 2026-09-29).

   D5: Bounded, Red Rose, Red Hat Display (300 + 400 latin) and Shippori Mincho (600) now live
   in Elementor Pro → Custom Fonts (docs/rebuild/decisions.md D5; post IDs in the overnight
   report) — self-hosted, font-display:swap (via the elementor_pro/custom_fonts/font_display
   filter in inc/assets.php), one upload each, no duplicate media. Their old @font-face rules
   were REMOVED from this file.

   What's left: Red Hat Display 400's LATIN-EXT subset (RedHatDisplay-Regular-ext.woff2, for the
   es/de/nl accented characters — 'é', 'ñ', 'ü'…). Custom Fonts' metabox has NO unicode-range
   field, so it can't express "two files split by codepoint range" — the one thing it genuinely
   can't do. Kept here, scoped to its real range, and enqueued (inc/assets.php,
   ageshio_fonts_enqueue) with a dependency on Elementor's own stylesheet handles so it prints
   AFTER Elementor's Custom Fonts CSS: per the CSS Fonts spec, when two @font-face rules for the
   same family/weight/style both nominally cover a codepoint, the LAST one declared wins — so
   this narrow, correctly-subsetted rule always wins for its own range, and the Custom Fonts
   400 entry (unrestricted range, but a latin-only file) is never asked to render a glyph it
   doesn't have. */
@font-face {
  font-family: 'Red Hat Display';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url('fonts/RedHatDisplay-Regular-ext.woff2') format('woff2');
  unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}