Skip to content

Add English and Japanese localization - #14

Open
keishingu wants to merge 2 commits into
JS00001:masterfrom
keishingu:codex/i18n-ja
Open

keishingu wants to merge 2 commits into
JS00001:masterfrom
keishingu:codex/i18n-ja

Conversation

@keishingu

@keishingu keishingu commented Sep 15, 2026

Copy link
Copy Markdown

Thanks for building such a great app! I鈥檇 love to help make HogLite accessible to more users.

Summary

  • add device-locale detection with expo-localization and translations with i18n-js
  • keep English as the source language and fallback, and add Japanese translations
  • localize navigation, onboarding, insights, activity, exceptions, settings, dialogs, errors, date ranges, numbers, and durations
  • declare English and Japanese in the iOS bundle configuration
  • keep event names, property keys, project/dashboard names, URLs, and API-provided content unchanged

The locale resolver maps ja and regional variants such as ja-JP to Japanese. Unsupported locales fall back to English. Translation keys are typed from the English locale so missing Japanese keys fail type checking.

expo-localization is pinned to 16.1.0, the lowest stable release that compiles with the current Xcode Swift SDK.

IMG_2147 IMG_2145

Verification

  • npx jest --runInBand --no-watchman
  • npx expo config --type public
  • Japanese UI checked on a physical iPhone using a local development build
  • unsupported locale fallback and localized date, number, and duration formatting covered by tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant