Design: Internationalization

[sampotts]

Create a design document for how we could implement internationalization, incorporating all feedback and suggestions so far.

[github-actions]

Planning Recommendations

This design doc is upstream of an entire cluster of implementation issues already open:

• Feature: Core i18n Types, Translator, and Registry #1363 — Core i18n Types, Translator, and Registry
• Feature: React i18n Layer (@videojs/react/i18n) #1364 — React i18n Layer
• Feature: HTML i18n Layer (@videojs/html/i18n) #1365 — HTML i18n Layer
• Feature: Opaque Translation Keys in Core UI Components #1366 — Opaque Translation Keys in Core UI Components
• Feature: Wire I18nController into UI Elements and Move Error Dialog Defaults to Core #1367 — Wire I18nController into UI Elements
• Feature: Built-in Locale Packs #1368 — Built-in Locale Packs
• Feature: CDN Build for i18n and Locales #1369 — CDN Build for i18n and Locales
• Feature: Update HTML Skin Templates with <media-text> #1370 — Update HTML Skin Templates with ``
• Feature: Browser Translation API Fallback #1372 — Browser Translation API Fallback
• Docs: i18n Concept Page, How-To Guides, and API Reference #1373 — i18n Docs (Concept Page, How-To Guides, API Reference)

Issue #1363 already references internal/design/i18n.md — this design doc task should produce or finalize that file and serve as the blocked-by anchor for all of the above.

Recommendations:

• Milestone: 26.2 (implementation issues are already scoped here)
• Epic: link to i18n epic if one exists
• Blocked-by: Design: Internationalization #1381 should be listed as a blocker for Feature: Core i18n Types, Translator, and Registry #1363–Docs: i18n Concept Page, How-To Guides, and API Reference #1373
• Priority: P1 — i18n is a prerequisite for all the implementation issues

[github-actions]

Reopened — this issue was closed by PR #1078 (docs(design): menus) but that PR only added internal/design/ui/menus.md. No i18n design document was created. The Closes #1381 in the PR body appears to have been a mistake.

This issue remains open: an internal/design/i18n.md document needs to be written before the implementation issues (#1363–#1373) can proceed.