Multi-language + multi-script storefront (Hindi, Arabic, Mandarin, Korean), how does Magento handle it?

Magento store views are how. One Magento instance, one product catalog, multiple store views, each with its own language pack, currency, payment methods, and translated content.

• Hindi (हिन्दी), Devanagari script. Load Noto Sans Devanagari font, subset by language, lazy-load so an English-speaking visitor doesn’t pay the cost. Translation lives in Magento i18n CSV files + per-product translated labels via the product attribute store-view override.
• Arabic (العربية), right-to-left layout. Magento has been RTL-aware since 2.3 (Hyvä theme since 1.3). Whole layout mirrors: nav, breadcrumbs, product image, checkout. CSS uses dir="rtl" at the HTML level + logical properties (margin-inline-start, etc.) for forward-compatible RTL.
• Mandarin (中文) + Korean (한국어), CJK scripts. Noto Sans SC / Noto Sans KR fonts, similar lazy-loading. Both LTR like English so no layout flip needed.
• Spanish, trivial (Latin script, LTR). Mostly translation work.

The pattern: English URL slugs everywhere (Google indexes English; diaspora users in the US still Google in English even if they read the PDP in Hindi). Translated H1, breadcrumbs, PDP descriptions, category labels, checkout strings. Customer auto-routes by Accept-Language header on first visit, then sticky on a store-view cookie. A “Change Language” switcher in the header.

Same SKU pool across all store views, do not duplicate products per language. That breaks reporting, inventory, and SEO. The translation lives at the attribute level, not the product level.