Languages

Language Coverage and Translation

Playbook RG is English-first, with some translated player resources. The coverage below lets teams tell a translated asset from a fully maintained local experience.

Current coverage

Coverage by Area

Website and Framework

English

Source language

The navigation, product pages, evidence summaries, and implementation guidance are maintained in English.

Player Website Template

English, Japanese, Simplified Chinese, Arabic

Available

The Arabic template includes right-to-left layout support. Deployments should still receive native-speaker review.

Player Collateral

English, Japanese, Simplified Chinese, Arabic

Varies by item

Check the individual asset before deployment; translated variants should stay paired with the same source version.

Myth Quiz Feeds

English, Japanese, Simplified Chinese, Arabic

20 quizzes per language

All four feeds share the September 6, 2026 edition and stable IDs, and the revised translations still need native-speaker review. Articles and social-card drafts are English only.

Academy: Two Public Programs

English, French, Spanish, Japanese, Simplified Chinese

Course menu options

All Employees and Brand Foundations list these language options. Check lesson text, audio, and downloads before assigning; language coverage for organization previews must be confirmed during setup.

Jurisdiction Modules

English

Reference layer

Modules document local requirements in English. Operators localize player-facing material during implementation and approval.

Translation standard

Release Rules for Translated Content

A language is ready for release when its whole player experience is ready, and the four rules below set out what that requires.

1

Priority for the Player Layer

Prioritize limits, odds, help information, game explanations, and required disclosures—the content people need to act safely. Translate marketing pages only when the core experience can ship with them.

2

Localization as Adaptation

Do not translate word for word. Preserve the meaning, reading level, tone, number and currency formats, examples, and local regulatory language.

3

Version Pairing

Every translated asset should name its source version, locale, review date, and reviewer. When the source changes materially, its translations return to review.

4

Human Review

Machine translation can support a draft, but a fluent reviewer should approve player-facing language. A local compliance reviewer should approve regulated statements and help information.

Why no global switcher yet?

The Risk of Partial Translation

A language option in the main navigation signals that the whole service is available in that language. Adding one before the core pages, disclosures, forms, and support paths have matching coverage would make the site harder to use.

The site-wide switcher should launch one locale at a time, after that locale has complete core navigation, essential product information, translated metadata, a tested fallback, and named owners for content and regulatory review.

To improve a translation or propose the next locale, open an issue in the public Playbook repository or email info@gamblingpolicy.com.